Java CVE-2026-33166
HIGHCVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Lifecycle Timeline
3Blast Radius
ecosystem impact- 1 maven packages depend on io.qameta.allure:allure-generator (1 direct, 0 indirect)
Ecosystem-wide dependent count for version 2.38.0.
DescriptionNVD
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
- Create a directory named allure-results.
- 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"
}
]
}- run
allure generate allure-results -o allure-report - The content of
/etc/passwdwill now be present inallure-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.
AnalysisAI
Path traversal in Allure report generator for Jenkins allows unauthenticated attackers to read arbitrary files from the host system by crafting malicious test result files with specially crafted attachment paths. The vulnerability stems from insufficient path validation when processing attachments during report generation, enabling sensitive files to be included in generated reports. …
Sign in for full analysis, threat intelligence, and remediation guidance.
RemediationAI
Within 24 hours: audit all CI/CD pipelines using Allure to identify exposure points, particularly those processing external contributions; disable Allure report generation for untrusted sources if feasible. Within 7 days: implement input validation on test result files before Allure processing, isolate Allure execution in restricted containers with minimal file system access, and rotate any credentials that may have been exposed. …
Sign in for detailed remediation steps.
More from same product – last 7 days
Arbitrary file disclosure in the Jenkins Email Extension Plugin (email-ext) versions 1933.v45cec755423f and earlier lets
Arbitrary file write in the Jenkins Credentials Binding Plugin (version 720.v3f6decef43ea_ and earlier) lets users who c
Arbitrary file read on the Jenkins controller is possible in the Jenkins 'Pipeline: Groovy Libraries Plugin' (version 79
Unsafe deserialization in Jenkins Active Directory Plugin 2.41 and earlier allows a remote attacker holding administrati
Server-Side Request Forgery in Jenkins Active Directory Plugin 2.41 and earlier enables a highly privileged attacker to
Share
External POC / Exploit Code
Leaving vuln.today
GHSA-64hm-gfwq-jppw