VulnerabilityPublished 26 Mar 2026

CVE-2026-33486: roadiz core-bundle-dev-app · Server-Side Request Forgery (SSRF)

Affects roadiz core-bundle-dev-appSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.8 Medium · fixed in 2.7.9 : update roadiz core-bundle-dev-app when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

6.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.7.9, 2.6.28, 2.5.44 +1

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade core-bundle-dev-app to 2.7.9, 2.6.28, 2.5.44 or 2.3.42; roadiz/core-bundle-dev-app to 2.3.42.

Affected software

Product	Affected	Fixed in
roadizcore-bundle-dev-app	Affected >=2.7.0 <2.7.9	Fixed in 2.7.9
roadizcore-bundle-dev-app	Affected >=2.6.0 <2.6.28	Fixed in 2.6.28
roadizcore-bundle-dev-app	Affected >=2.4.0 <2.5.44	Fixed in 2.5.44
roadizcore-bundle-dev-app	Affected <2.3.42	Fixed in 2.3.42
GitHubroadiz/core-bundle-dev-app`pkg:github/roadiz/core-bundle-dev-app`Other threats	Affected <2.3.42	Fixed in 2.3.42

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-33486, organizations should immediately upgrade Roadiz core-bundle-dev-app to the patched versions 2.7.9, 2.6.28, 2.5.44, or 2.3.42 depending on their current version. In addition to patching, administrators should audit user accounts and permissions to ensure that only trusted users have authentication access, reducing the risk of insider threats or compromised credentials. Implement network segmentation and firewall rules to limit internal server access and restrict unnecessary outbound requests from the web server. Enable logging and monitoring to detect unusual file access patterns or SSRF attempts. Employ web application firewalls (WAFs) with SSRF detection capabilities to block malicious requests. Regularly review and rotate sensitive credentials and environment variables to minimize the impact of potential leaks. Finally, conduct security awareness training for administrators and users to recognize and report suspicious activities related to internal resource access.

Description

Roadiz is a polymorphic content management system based on a node system that can handle many types of services. A vulnerability in roadiz/documents prior to versions 2.7.9, 2.6.28, 2.5.44, and 2.3.42 allows an authenticated attacker to read any file on the server's local file system that the web server process has access to, including highly sensitive environment variables, database credentials, and internal configuration files. Versions 2.7.9, 2.6.28, 2.5.44, and 2.3.42 contain a patch.

Impact

The primary impact of CVE-2026-33486 is the unauthorized disclosure of sensitive information stored on the server hosting the Roadiz CMS. Attackers who successfully exploit this vulnerability can access environment variables, database credentials, and internal configuration files, which may enable further attacks such as privilege escalation, lateral movement, or data exfiltration. Although the vulnerability does not directly affect data integrity or system availability, the confidentiality breach can lead to severe consequences including compromise of backend databases, exposure of user data, and potential disruption of business operations. Organizations relying on Roadiz CMS for content management may face increased risk of targeted attacks, especially if the exposed credentials are reused across other systems. The requirement for authentication limits the attack surface to insiders or compromised accounts, but the medium CVSS score and scope change indicate a notable security risk that must be addressed promptly.

CWE-918Server-Side Request Forgery (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Implementation · Operation
If there is a known list of applications, IP, hostname, and/or domains to which the product is allowed to communicate, then use allowlists to ensure that outgoing requests are restricted to these known entities. The allowlists could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Operation
If the product is expected to be able to connect to arbitrary IP addresses or domains, consider using a denylist that includes private network addresses, internal domain names, etc. The denylist could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Mar 2026, 18:02 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats