VulnerabilityPublished 6 Aug 2026

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

Affects contao/contaoSource GCVE Database

Compare

Not known to be exploited · CVSS 3.1 Low : upgrade to 5.7.7 when convenient.

Data as of 6 Nov 2026, 23:24 UTC

CVSS 3.1 base score

3.1Low

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5.7.7

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 6 Aug 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 6 Nov 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 contao/contao and contao/core-bundle to 5.7.7.

Affected software

Product	Affected	Fixed in
Packagistcontao/contao	Affected >=5.7.0 <5.7.7	Fixed in 5.7.7
Packagistcontao/core-bundle	Affected >=5.7.0 <5.7.7	Fixed in 5.7.7

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

AI-suggested

A patch is available for this vulnerability. The vendor recommends rejecting slashes, backslashes, NUL characters, and dot-segment components in the attachment identifier to treat it strictly as a filename. Additionally, route requirements should prevent slashes in the identifier. After path resolution, the system must verify that the canonical relative path starts with the authorized job UUID directory before allowing access. The same validation should be applied when adding attachments to prevent writing outside the authorized job directory. Users should apply the official fix in versions 5.7.7 or later.

Description

Contao versions 5.7.0 through 5.7.6 contain a path traversal vulnerability in the job attachment download endpoint. An authenticated backend user with access to one job can manipulate the attachment identifier to read files from other job directories within the job attachments storage. This occurs because the system canonicalizes the combined path but does not enforce that the resolved path remains within the authorized job directory. The vulnerability allows reading of attachments such as CSV logs from other jobs if the attacker knows the target job UUID and attachment filename.

Impact

An authenticated backend user with access to one job can read attachments belonging to other jobs if they know or can guess the target job UUID and attachment filename. This leads to unauthorized disclosure of potentially sensitive job-related files such as debug logs and crawler job CSV logs containing URLs, referring URLs, tags, and error messages. The impact is limited by the need for authentication and knowledge of valid job UUIDs and filenames. The CVSS score is 3.1 (Low), reflecting low confidentiality impact and high attack complexity.

Summary

The vulnerability in Contao's JobsController::downloadJobAttachment allows an authenticated backend user to bypass authorization checks for job attachments by exploiting path traversal in the attachment identifier. The controller authorizes access only based on the job UUID route parameter, but the attachment identifier is attacker-controlled and concatenated with the authorized job UUID before path canonicalization. The VirtualFilesystem::resolve method canonicalizes the path and rejects absolute or leading '..' segments but does not ensure the resolved path stays within the authorized job directory. This enables reading files from other job directories inside var/job-attachments by using '../' segments in the identifier. The vulnerability affects Contao versions >=5.7.0 and <5.7.7. The recommended fix involves treating the attachment identifier strictly as a filename, rejecting slashes and dot-segments, enforcing route requirements to prevent slashes, and verifying the resolved path starts with the authorized job UUID.

CWE-22Improper Limitation of a Pathname to a Restricted Directory (Path Traversal) (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
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.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (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 7 Aug 2026, 06:13 UTC

WeaknessesCWE-22

Technical details

References

Community reviews

Related threats