| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-64hm-gfwq-jppw | Allure Report has an Arbitrary File Read via Path Traversal in Attachment Processing (Allure 1, Allure 2, and XCTest Readers) |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 24 Mar 2026 02:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 23 Mar 2026 10:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Allure-framework
Allure-framework allure2 |
|
| Vendors & Products |
Allure-framework
Allure-framework allure2 |
Fri, 20 Mar 2026 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Allure Report has an Arbitrary File Read via Path Traversal in Attachment Processing (Allure 1, Allure 2, and XCTest Readers) | |
| Weaknesses | CWE-22 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-03-24T02:04:09.955Z
Reserved: 2026-03-17T21:17:08.888Z
Link: CVE-2026-33166
Updated: 2026-03-24T02:04:06.012Z
Status : Awaiting Analysis
Published: 2026-03-20T22:16:28.660
Modified: 2026-03-23T14:32:02.800
Link: CVE-2026-33166
No data.
OpenCVE Enrichment
Updated: 2026-03-23T09:52:35Z
Github GHSA