# CVE-2026-55825: Contao: Possible path traversal in job download URIs

> Authenticated backend users can read files from other job directories via path traversal in attachment URIs, bypassing cross-job authorization.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-grm4-wm43-9jh5

## What is CVE-2026-55825?

CVE-2026-55825 is a low-severity path traversal vulnerability in contao, published on 31 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Contao is an Open Source CMS. In versions 5.7.0 through 5.7.6, an authenticated backend user who can access one job can request an attachment identifier containing ../ segments and make the job attachment download endpoint read a file from another job directory inside var/job-attachments. The controller authorizes only the jobUuid route parameter. The later attachment lookup joins that authorized job UUID with the attacker-controlled identifier, then passes the combined path to the virtual filesystem. VirtualFilesystem::resolve() canonicalizes the whole path and only rejects paths that escape the filesystem mount, so authorized-job/../victim-job/debug_log.csv becomes victim-job/debug_log.csv. This is a cross-job authorization bypass for known job attachment paths. It is not a practical brute-force against unknown jobs because job directories are UUID v4 values.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

4 open source packages ship an affected version, including contao/contao and contao/core-bundle.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `contao/contao` | Packagist | From 5.7.0 | 5.7.7 |
| `contao/contao` | Packagist | From 5.7.0 | 5.7.7 |
| `contao/core-bundle` | Packagist | From 5.7.0 | 5.7.7 |
| `contao/core-bundle` | Packagist | From 5.7.0 | 5.7.7 |

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

Upgrade contao/contao to 5.7.7 or later.

## Is CVE-2026-55825 being exploited?

There is no known exploitation of CVE-2026-55825 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55825 is a low-severity path traversal vulnerability in contao, published on 31 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-55825 in the wild and no public exploit code.

Affected packages and fixed versions:
- contao/contao (Packagist): affected from 5.7.0; fixed in 5.7.7
- contao/contao (Packagist): affected from 5.7.0; fixed in 5.7.7
- contao/core-bundle (Packagist): affected from 5.7.0; fixed in 5.7.7
- contao/core-bundle (Packagist): affected from 5.7.0; fixed in 5.7.7

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-55825/ (Markdown: https://insights.sbomify.com/CVE-2026-55825/index.md)
```

## Sources

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

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