CVE-2026-55825: Contao: Possible path traversal in job download URIs
Summary 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.
Published Aug 6, 2026
Affected packages
contao/contao
- Ecosystem
- Composer (PHP)
- Affected
- >= 5.7.0, < 5.7.7
- Fixed in
- 5.7.7
- Check
composer show contao/contao
contao/core-bundle
- Ecosystem
- Composer (PHP)
- Affected
- >= 5.7.0, < 5.7.7
- Fixed in
- 5.7.7
- Check
composer show contao/core-bundle
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
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.
Root Cause
JobsController::downloadJobAttachment() checks access to the route jobUuid before loading the attachment:
$job = $this->jobs->getByUuid($jobUuid);
if (!$job || !$this->jobs->hasAccess($job)) {
throw $this->createNotFoundException();
}
$attachment = $this->jobs->getAttachment($jobUuid, $identifier);Jobs::getAttachment() then resolves a path built from the authorized job UUID and the attacker-controlled identifier:
$fileItem = $this->jobAttachmentsStorage->get($this->getAttachmentIdentifier($job, $identifier));return $job->getUuid().'/'.$identifier;VirtualFilesystem::resolve() canonicalizes the combined path. It rejects absolute paths and paths that start with .., but it does not preserve the authorized job directory as a boundary:
$path = Path::canonicalize($location);
if (str_starts_with($path, '..')) {
throw new \OutOfBoundsException(...);
}
return Path::join($this->prefix, $path);Therefore:
<authorized-job>/../<victim-job>/debug_log.csvcanonicalizes to:
<victim-job>/debug_log.csvwhich remains inside the job-attachments filesystem mount and is accepted.
Recommended Fix
Treat the attachment identifier as a filename, not a path:
- Reject
/,\, NUL, and dot-segment components inidentifier. - Add a route requirement that prevents slashes in
{identifier}if nested attachment paths are not intended. - After resolving, assert the canonical relative path starts with
<authorized-job-uuid>/before returning aFilesystemItem. - Apply the same identifier validation in
Jobs::addAttachment()so future producers/extensions cannot write outside the owning job directory.
Impact
A low-privileged backend user can read another job's attachment if they know or obtain the target job UUID and attachment filename. Built-in crawler jobs attach CSV logs such as debug_log.csv, broken-link-checker_log.csv, and search-index_log.csv, which can contain crawled URLs, referring URLs, tags, and error messages.
Credited to 0x1saac.
References
- https://github.com/contao/contao/security/advisories/GHSA-grm4-wm43-9jh5
- https://nvd.nist.gov/vuln/detail/CVE-2026-55825
- https://contao.org/en/security-advisories/path-traversal-in-the-jobs-module
- https://github.com/FriendsOfPHP/security-advisories/blob/master/contao/contao/CVE-2026-55825.yaml
- https://github.com/FriendsOfPHP/security-advisories/blob/master/contao/core-bundle/CVE-2026-55825.yaml
- https://github.com/advisories/GHSA-grm4-wm43-9jh5
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-104882
contao/core-bundle: Improper access control in the CSV import wizard
medium6.5Nov 20, 2026CVE-2026-104883
contao/core-bundle: Non-admin users can self-grant permissions that implicitly make them administrators
high7.2Nov 20, 2026CVE-2026-104884
contao/core-bundle: Cross-site scripting in the frontend search results
medium5.4Nov 20, 2026CVE-2026-107842
Contao: Protected page content is disclosed to anonymous visitors after contao.search.index_protected is disabled
medium5.3Oct 9, 2026CVE-2026-107843
Contao: The registration module re-sends activation mails
medium5.3Oct 9, 2026CVE-2026-107844
Contao: Path traversal in the images controller
medium5.3Oct 9, 2026
