Allure: Path Traversal in Allure Report HTTP Server Allows Arbitrary File Read
Key facts
- Attack vector
- Local
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-22 and the CVSS impact.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| allure-framework | allure2 | before 2.39.0 | 2.39.0 | Patch available | CNA |
| — | io.qameta.allure:allure-commandline (Maven) | before 2.39.0 | 2.39.0 | Patch available | GHSA-82cg-3hv7-74gc |
- allure2 Vendorallure-framework Affected before 2.39.0 Fixed in 2.39.0 Patch available CNA
- io.qameta.allure:allure-commandline (Maven) Vendor— Affected before 2.39.0 Fixed in 2.39.0 Patch available GHSA-82cg-3hv7-74gc
Remediation
- Fix · CNA allure2 (allure-framework) Fixed in 2.39.0
- Fix · GHSA-82cg-3hv7-74gc io.qameta.allure:allure-commandline (Maven) Fixed in 2.39.0 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2026-55846
- 2026-10-03 Alias added: GHSA-82cg-3hv7-74gc
References
Other 5
- https://github.com/allure-framework/allure2/security/advisories/GHSA-82cg-3hv7-74gc
- https://github.com/allure-framework/allure2/pull/3288
- https://github.com/allure-framework/allure2/commit/e83cd67658bc2266832ab366eadd0bc1f48baced
- https://github.com/allure-framework/allure2/releases/tag/2.39.0
- https://github.com/allure-framework/allure2
More allure-framework vulnerabilities
- TI-2025-32924 Allure 2's xunit-xml-plugin Vulnerable to Improper XXE Restriction CVSS 3.1HIGH 7.5
- TI-2026-40309 Allure: Stored XSS via unescaped ANSI helper in Allure report status message/trace rendering CVSS 3.1MEDIUM 6.1
Sources
- CVE-2026-55846 · CVE Program
- CVE-2026-55846 · NVD
- FIRST EPSS
- GHSA-82cg-3hv7-74gc · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences