CVE-2026-33166
Path Traversal in Allure Report 2.x Allows Arbitrary File Read
Publication date: 2026-03-20
Last updated on: 2026-04-14
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| qameta | allure_report | to 2.38.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in Allure Report version 2.x prior to 2.38.0 allows an attacker to perform an arbitrary file read through path traversal. This happens when the report generator processes test result files. An attacker can create a malicious result file that references a sensitive file on the host system as an attachment source. When the report is generated, Allure resolves these paths and includes the sensitive file contents in the final report.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized disclosure of sensitive files on the host system. An attacker exploiting this flaw can access confidential information by crafting malicious test result files that cause Allure to include sensitive data in generated reports. This can compromise the confidentiality of data and potentially expose critical information to unauthorized parties.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade Allure Report to version 2.38.0 or later, as this version fixes the arbitrary file read via path traversal issue.