CVE-2026-33166: Allure generator Path Traversal Vulnerability

HIGH
Advisory Identifier: GHSA-64hm-gfwq-jppw
CVSS 8.6
CWE-22
Published
Advisory Summary

CVE-2026-33166 is a HIGH (CVSS 8.6) path traversal vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Allure generator libraries in the Maven ecosystem. The issue involves allure report has an arbitrary file read via path traversal in attachment processing (allure 1, allure 2, and xctest readers). Remediation is available by upgrading affected packages to version 2.38.0.

CVE-2026-33166 at a Glance

CVE Identifier CVE-2026-33166
GHSA Identifier GHSA-64hm-gfwq-jppw
Severity HIGH
CVSS v3.1 Base Score 8.6
CWE Classification CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product Allure generator
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 8.6

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-33166

To remediate this vulnerability, upgrade all affected Allure generator dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

io.qameta.allure:allure-generator fixed: 2.38.0
<dependency>
    <groupId>io.qameta.allure</groupId>
    <artifactId>allure-generator</artifactId>
    <version>2.38.0</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=io.qameta.allure

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-33166, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=io.qameta.allure

Analyze the terminal output to locate any version of Allure generator in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.38.0), your application is affected.

Note: The mvn dependency:tree -Dincludes=io.qameta.allure command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where 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. In Allure generator, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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.

CVE-2026-33166 Affected Allure generator Versions

1 component(s)
Fixed Versions:
2.38.0
Product / Package Ecosystem Affected Versions Fixed Version
io.qameta.allure:allure-generator
Maven
< 2.38.0
2.38.0

References

Frequently Asked Questions

What is CVE-2026-33166?
CVE-2026-33166 is a security vulnerability in Allure generator involving Allure Report has an Arbitrary File Read via Path Traversal in Attachment Processing (Allure 1, Allure 2, and XCTest Readers) under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which Allure generator versions are affected?
Affected versions include releases prior to 2.38.0 across affected packages: io.qameta.allure:allure-generator.
What version fixes CVE-2026-33166?
Upgrading to 2.38.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is allure-generator affected?
Yes, io.qameta.allure:allure-generator is affected in releases prior to 2.38.0. Upgrade your dependency to 2.38.0 or later.
What is the CVSS score of CVE-2026-33166?
CVE-2026-33166 has a CVSS v3.1 base score of 8.6 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N.
What CWE is associated with CVE-2026-33166?
CVE-2026-33166 is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (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.).
How can I check Maven dependencies for CVE-2026-33166?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=io.qameta.allure'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-64hm-gfwq-jppw",
  "modified" : "2026-03-25T18:11:28Z",
  "published" : "2026-03-18T19:53:59Z",
  "aliases" : [ "CVE-2026-33166" ],
  "summary" : "Allure Report has an Arbitrary File Read via Path Traversal in Attachment Processing (Allure 1, Allure 2, and XCTest Readers)",
  "details" : "### Summary\nThe 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.\n\n### Details\nThe 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.\n\nAffected Files and Lines:\n\nAllure2Plugin.java (Line 264): `final Path attachmentFile = source.resolve(attachment.getSource());`\n\nAllure1Plugin.java (Line 328): `final Path attachmentFile = source.resolve(attachment.getSource());`\n\nXcTestPlugin.java (Line 181): `attachments.resolve(String.format(\"Screenshot_%s.%s\", uuid, ext))`\n\nSince `resolve()` allows absolute paths or ../ sequences to escape the base directory, any file readable by the process can be exfiltrated.\n\n### PoC\n1) Create a directory named allure-results.\n\n2) Create a file malicious-result.json inside it:\n\n```\n{\n  \"uuid\": \"poc-traversal\",\n  \"name\": \"Path Traversal PoC\",\n  \"status\": \"passed\",\n  \"attachments\": [\n    {\n      \"name\": \"Sensitive Data\",\n      \"source\": \"../../../../../../../../../../../etc/passwd\",\n      \"type\": \"text/plain\"\n    }\n  ]\n}\n```\n3) run `allure generate allure-results -o allure-report`\n\n4) The content of `/etc/passwd` will now be present in `allure-report/data/attachments/`.\n\n\n### Impact\nThis 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "io.qameta.allure:allure-generator"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.38.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2.37.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/allure-framework/allure2/security/advisories/GHSA-64hm-gfwq-jppw"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-33166"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/allure-framework/allure2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-18T19:53:59Z",
    "nvd_published_at" : "2026-03-20T22:16:28Z"
  }
}