CVE-2026-33166 Allure Report has an Arbitrary File Read via Path Traversal in Attachment Processing (Allure 1, Allure 2, and XCTest Readers)
An attacker can read sensitive files on the host system by crafting malicious test result files processed by Allure Report.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-33166?
CVE-2026-33166 is a high-severity path traversal vulnerability in allure-framework allure2, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Allure 2 is the version 2.x branch of Allure Report, a multi-language test reporting tool. The Allure report generator prior to version 2.38.0 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. Version 2.38.0 fixes the issue.
Weakness: CWE-22
Which versions are affected by CVE-2026-33166?
2 open source packages ship an affected version, including io.qameta.allure:allure-generator. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
io.qameta.allure:allure-generator Maven | All versions | 2.38.0 |
io.qameta.allure:allure-generator Maven | All versions | 2.38.0 |
Products include Qameta Allure Report.
How do I fix CVE-2026-33166?
Upgrade io.qameta.allure:allure-generator to 2.38.0 or later.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-33166 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33166 exists.
Sources
Also known as GHSA-64hm-gfwq-jppw.