CVE-2026-33166: io.qameta.allure:allure-generator Arbitrary File Read via Path Traversal

Summary

18/03/2026
Yes i
High
8.6

CVE-2026-33166: The Allure report generator is vulnerable to an arbitrary file read via path traversal when processing test results. Affects io.qameta.allure:allure-generator versions < 2.38.0. Fixed in 2.38.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The Allure report generator is a popular tool used for generating test reports in various testing frameworks. It provides a comprehensive overview of test results, including detailed information about test cases, their statuses, and attachments such as screenshots and logs. However, it is vulnerable to an arbitrary file read due to improper handling of file paths during attachment processing.

Vulnerability Detail

The vulnerability arises from the way the Allure report generator resolves attachment paths using unvalidated user input. Specifically, the code utilizes Path.resolve() without normalizing the path or ensuring that the resulting file remains within the intended results directory. This oversight allows attackers to craft malicious result files that can point to sensitive files on the host system, leading to potential data exfiltration. The impact is particularly severe in CI/CD environments, where an attacker could exploit this vulnerability to access server secrets, cloud credentials, or environment configuration files stored on the runner disk.

How To Fix

Minimum fixed version

2.38.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary measure, avoid using attachment sources that include absolute paths or .. sequences. Ensure that any result files processed by Allure do not contain references to sensitive files outside the intended directory.

Conclusion

CVE-2026-33166 represents a significant security risk for users of the Allure report generator, particularly in automated testing environments. It is crucial to update to the patched version to mitigate the risk of data exfiltration and ensure the security of sensitive information.

See every vulnerability recorded for io.qameta.allure:allure-generator →

Share this vulnerability

FAQ

CVE-2026-33166 is a vulnerability in the Allure report generator that allows arbitrary file reads via path traversal during attachment processing.

An attacker could exploit this vulnerability to exfiltrate sensitive information such as server secrets or cloud credentials from the CI/CD runner.

Versions of io.qameta.allure:allure-generator up to 2.37.0 are affected by this vulnerability.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can use the Vulert playground at Vulert Scanner without any signup.

The CVSS score of this vulnerability is 8.6, indicating a high severity level.

Related vulnerabilities

Recent vulnerabilities recorded for io.qameta.allure:allure-generator.

How To Fix

Minimum fixed version

2.38.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback