# CVE-2026-33486: Roadiz has Server-Side Request Forgery (SSRF) in roadiz/documents

> Authenticated attackers can exploit SSRF in Roadiz to read sensitive local files, including credentials and configuration data.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Mar 2026
- **Updated:** 26 Mar 2026
- **Also known as:** GHSA-rc55-58f4-687g

## What is CVE-2026-33486?

CVE-2026-33486 is a medium-severity server-side request forgery vulnerability in roadiz core-bundle-dev-app, published on 26 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-33486?

8 open source packages ship an affected version, including roadiz/documents. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `roadiz/documents` | Packagist | All versions | 2.3.42 |
| `roadiz/documents` | Packagist | All versions | 2.3.42 |
| `roadiz/documents` | Packagist | From 2.4.0 | 2.5.44 |
| `roadiz/documents` | Packagist | From 2.4.0 | 2.5.44 |
| `roadiz/documents` | Packagist | From 2.6.0 | 2.6.28 |
| `roadiz/documents` | Packagist | From 2.6.0 | 2.6.28 |
| `roadiz/documents` | Packagist | From 2.7.0 | 2.7.9 |
| `roadiz/documents` | Packagist | From 2.7.0 | 2.7.9 |

Products: Roadiz Core-Bundle-Dev-App.

## How do I fix CVE-2026-33486?

Upgrade roadiz/documents to a fixed version for your release line: 2.3.42, 2.5.44, 2.6.28 or 2.7.9.

## Is CVE-2026-33486 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33486 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33486 and fix it if it is affected.

What it is: CVE-2026-33486 is a medium-severity server-side request forgery vulnerability in roadiz core-bundle-dev-app, published on 26 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33486 exists.

Affected packages and fixed versions:
- roadiz/documents (Packagist): affected all versions; fixed in 2.3.42
- roadiz/documents (Packagist): affected all versions; fixed in 2.3.42
- roadiz/documents (Packagist): affected from 2.4.0; fixed in 2.5.44
- roadiz/documents (Packagist): affected from 2.4.0; fixed in 2.5.44
- roadiz/documents (Packagist): affected from 2.6.0; fixed in 2.6.28
- roadiz/documents (Packagist): affected from 2.6.0; fixed in 2.6.28
- roadiz/documents (Packagist): affected from 2.7.0; fixed in 2.7.9
- roadiz/documents (Packagist): affected from 2.7.0; fixed in 2.7.9

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33486/ (Markdown: https://insights.sbomify.com/CVE-2026-33486/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33486
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33486
- OSV: https://osv.dev/vulnerability/CVE-2026-33486

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33486/
Summaries are generated and may contain mistakes; the official description above is the record.