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.
References
| Link | Resource |
|---|---|
| https://github.com/allure-framework/allure2/security/advisories/GHSA-64hm-gfwq-jppw | Exploit Vendor Advisory |
Configurations
History
14 Apr 2026, 18:42
| Type | Values Removed | Values Added |
|---|---|---|
| Summary |
|
|
| CPE | cpe:2.3:a:qameta:allure_report:*:*:*:*:*:*:*:* | |
| References | () https://github.com/allure-framework/allure2/security/advisories/GHSA-64hm-gfwq-jppw - Exploit, Vendor Advisory | |
| First Time |
Qameta allure Report
Qameta |
20 Mar 2026, 22:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-03-20 22:16
Updated : 2026-04-14 18:42
NVD link : CVE-2026-33166
Mitre link : CVE-2026-33166
CVE.ORG link : CVE-2026-33166
JSON object : View
Products Affected
qameta
- allure_report
CWE
CWE-22
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
