CVE-2026-55847 Allure: Stored XSS via unescaped ANSI helper in Allure report status message/trace rendering
Attackers can inject malicious scripts into Allure reports via crafted test results, leading to arbitrary JavaScript execution when users view the report.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-55847?
CVE-2026-55847 is a medium-severity cross-site scripting vulnerability in allure-framework allure-generator, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
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 ansi.js helper at allure-generator/src/main/javascript/helpers/ansi.js passes attacker-influenced statusMessage and statusTrace values through AnsiToHtml without HTML escaping and wraps the result in Handlebars SafeString, disabling template auto-escaping in allure-generator/src/main/javascript/blocks/status-details/status-details.hbs. JunitXmlPlugin.java can populate these fields directly from crafted JUnit XML failure messages and traces, and equivalent input flows exist in the TRX, xUnit XML, xctest, and Allure1 and Allure2 plugins. When a user views the affected status details, unescaped markup executes arbitrary JavaScript in the report origin, which can expose report data and compromise sessions associated with that origin. This is an incomplete-fix case because PR 3271 escaped link helpers but did not address the ANSI helper. This issue is fixed in version 2.39.0.
Weakness: CWE-79
Which versions are affected by CVE-2026-55847?
2 open source packages ship an affected version, including io.qameta.allure:allure-generator.
| Package | Affected | Fixed in |
|---|---|---|
io.qameta.allure:allure-generator Maven | All versions | 2.39.0 |
io.qameta.allure:allure-generator Maven | All versions | 2.39.0 |
How do I fix CVE-2026-55847?
Upgrade io.qameta.allure:allure-generator to 2.39.0 or later.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-55847 being exploited?
There is no known exploitation of CVE-2026-55847 in the wild and no public exploit code.
Sources
Also known as GHSA-gx93-m64w-5m6h, UBUNTU-CVE-2026-55847.