Allure: Path Traversal in Allure Report HTTP Server Allows Arbitrary File Read (CVE-2026-55846) | HOL Guard CVE

Medium severityCVE-2026-55846GHSA-82CG-3HV7-74GC

Allure: Path Traversal in Allure Report HTTP Server Allows Arbitrary File Read

Answer in brief

CVE-2026-55846 records a Medium severity vulnerability in Allure: Path Traversal in Allure Report HTTP Server Allows Arbitrary File Read. The current sources do not mark it as known exploited. The current feed maps allure-framework/allure2 (generic), io.qameta.allure:allure-commandline (maven). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 14, 2026Updated Sep 14, 2026Source checked Sep 14, 2026First seen by HOL Jun 19, 2026Material review Sep 14, 2026

Upstream Advisory

Key facts

Risk: Medium
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps allure-framework/allure2 (generic), io.qameta.allure:allure-commandline (maven). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
allure-framework/allure2generic	< 2.39.0	Not reported
io.qameta.allure:allure-commandlinemaven	<=2.38.1	2.39.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for allure-framework/allure2, io.qameta.allure:allure-commandline.
Review the reported fix. Update io.qameta.allure:allure-commandline to 2.39.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Jun 19, 2026

Sources and claim methodology

Upstream source description

Allure 2 is the version 2.x branch of Allure Report, a multi-language test reporting tool. Prior to 2.39.0, the HTTP server started by allure serve and allure open uses URI.getPath() in Commands.setUpServer() in allure-commandline/src/main/java/io/qameta/allure/Commands.java and passes the percent-decoded request path to reportDirectory.resolve() without normalizing the result or confirming that it remains inside that directory. An unauthenticated client that can reach the server can submit parent-directory segments, including percent-encoded segments, and cause serveFile() to return any regular file readable by the Allure process. The server binds to localhost by default, but the --host option can expose it to other systems, and local users, adjacent containers, or browser-origin attacks may reach a local listener. This can disclose credentials, configuration, source code, build secrets, and other CI/CD data. This issue is fixed in version 2.39.0.

Quoted source text, attributed separately from HOL analysis.