CVE-2026-33166 is a high-severity path traversal vulnerability in io.qameta.allure:allure-generator (maven), affecting versions <= 2.37.0. It is fixed in 2.38.0.
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: 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.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
CVE-2026-33166 has a CVSS score of 8.6 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (2.38.0). Upgrading removes the vulnerable code path.
maven
io.qameta.allure:allure-generator (<= 2.37.0)io.qameta.allure:allure-generator → 2.38.0 (maven)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-33166 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-33166 is reachable in your applications. Get a demo
Upgrade io.qameta.allure:allure-generator to 2.38.0 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-33166 is a high-severity path traversal vulnerability in io.qameta.allure:allure-generator (maven), affecting versions <= 2.37.0. It is fixed in 2.38.0. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
CVE-2026-33166 has a CVSS score of 8.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
io.qameta.allure:allure-generator (maven) versions <= 2.37.0 is affected.
Yes. CVE-2026-33166 is fixed in 2.38.0. Upgrade to this version or later.
Whether CVE-2026-33166 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade io.qameta.allure:allure-generator to 2.38.0 or later.