# CVE-2026-55846: Allure: Path Traversal in Allure Report HTTP Server Allows Arbitrary File Read

> An unauthenticated attacker can read arbitrary files from the server via path traversal in the Allure Report HTTP server, potentially exposing sensitive CI/CD data.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-82cg-3hv7-74gc, UBUNTU-CVE-2026-55846

## What is CVE-2026-55846?

CVE-2026-55846 is a medium-severity path traversal vulnerability in allure-framework allure2, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-55846?

2 open source packages ship an affected version, including io.qameta.allure:allure-commandline.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.qameta.allure:allure-commandline` | Maven | All versions | 2.39.0 |
| `io.qameta.allure:allure-commandline` | Maven | All versions | 2.39.0 |

## How do I fix CVE-2026-55846?

Upgrade io.qameta.allure:allure-commandline to 2.39.0 or later.

## Is CVE-2026-55846 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55846 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55846 and fix it if it is affected.

What it is: CVE-2026-55846 is a medium-severity path traversal vulnerability in allure-framework allure2, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55846 exists.

Affected packages and fixed versions:
- io.qameta.allure:allure-commandline (Maven): affected all versions; fixed in 2.39.0
- io.qameta.allure:allure-commandline (Maven): affected all versions; fixed in 2.39.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55846/ (Markdown: https://insights.sbomify.com/CVE-2026-55846/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55846
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55846
- OSV: https://osv.dev/vulnerability/CVE-2026-55846

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55846/
Summaries are generated and may contain mistakes; the official description above is the record.