Loading...
Skip to main content

CVE-2026-33166 — Vulnerability in...

HIGH

Allure Report has an Arbitrary File Read via Path Traversal in Attachment Processing (Allure 1, Allure 2, and XCTest Readers)

Published March 18, 2026Updated March 25, 2026Source: osv

Summary

### Summary The Allure report generator is vulnerable to an arbitrary file read via path traversal when processing test results. An attacker can craft a malicious result file (-result.json, -container.json, or .plist) that points an attachment source to a sensitive file on the host system. During report generation, Allure will resolve these paths and include the sensitive files in the final report. ### Details The vulnerability exists in several plugins where attachment paths are resolved using unvalidated user input. The code uses Path.resolve() without normalizing the path or checking if the resulting file remains within the intended results directory. Affected Files and Lines: Allure2Plugin.java (Line 264): `final Path attachmentFile = source.resolve(attachment.getSource());` Allure1Plugin.java (Line 328): `final Path attachmentFile = source.resolve(attachment.getSource());` XcTestPlugin.java (Line 181): `attachments.resolve(String.format("Screenshot_%s.%s", uuid, ext))` Since `resolve()` allows absolute paths or ../ sequences to escape the base directory, any file readable by the process can be exfiltrated. ### PoC 1) Create a directory named allure-results. 2) Create a file malicious-result.json inside it: ``` { "uuid": "poc-traversal", "name": "Path Traversal PoC", "status": "passed", "attachments": [ { "name": "Sensitive Data", "source": "../../../../../../../../../../../etc/passwd", "type": "text/plain" } ] } ``` 3) run `allure generate allure-results -o allure-report` 4) The content of `/etc/passwd` will now be present in `allure-report/data/attachments/`. ### Impact This is a High Severity vulnerability. In CI/CD environments (GitHub Actions, Jenkins), an attacker submitting a Pull Request can exfiltrate server secrets, cloud credentials, or environment configuration files stored on the runner disk. It also may affect custom Allure web services where users can upload results, allowing them to read arbitrary files from the server's filesystem. Allure TestOps is not affected.

Advisory Timeline

  • First published March 18, 2026 (208 days ago).
  • Last revised March 25, 2026 — 7 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Maven
Update io.qameta.allure:allure-generator to 2.38.0 or later
<!-- Update pom.xml dependency version to 2.38.0 for io.qameta.allure:allure-generator -->

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (1)

Affects 1 ecosystem: maven (1).

PackageEcosystemAffectedFixed In
io.qameta.allure:allure-generator
maven
2.0-BETA8, 2.0.0, 2.0.1, 2.1.1 (+64 more)2.38.0

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 8.6 score means for each attack dimension.

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

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

Frequently Asked Questions

What is CVE-2026-33166?
Allure Report has an Arbitrary File Read via Path Traversal in Attachment Processing (Allure 1, Allure 2, and XCTest Readers) This vulnerability has been assigned a severity rating of HIGH (CVSS score: 8.6/10).
How do I check if my project is affected by CVE-2026-33166?
CVE-2026-33166 affects io.qameta.allure:allure-generator. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-33166 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
8.6

High exploitability or significant impact. Prioritize remediation within days.

Also Known As

GHSA-64hm-gfwq-jppw

Related CVEs

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies