CVE-2026-55847 is a medium-severity cross-site scripting (XSS) vulnerability in io.qameta.allure:allure-generator (maven), affecting versions <= 2.38.1. It is fixed in 2.39.0.
Summary The ansi.js Handlebars helper in allure-generator passes user-controlled statusMessage and statusTrace values from test result files through the ansi-to-html library and wraps the output in Handlebars SafeString without HTML escaping. Since ansi-to-html does not escape HTML entities by default, an attacker who can influence test result content (e.g., via crafted JUnit XML failure messages) can inject arbitrary JavaScript that executes when anyone views the generated Allure report. Details The vulnerability is an incomplete fix, commit 4c64b19 (PR #3271) fixed XSS in linky.js and text-with-links.js by adding escapeExpression(), but the same pattern in ansi.js was not addressed. Vulnerable sink, allure-generator/src/main/javascript/helpers/ansi.js:10-11: The AnsiToHtml constructor at line 4 does not set escapeForHtml: true: The ansi-to-html library (v0.7.2) defaults escapeForHtml to false, meaning HTML entities in the input pass through unchanged. Wrapping the result in SafeString tells Handlebars to skip its auto-escaping, so the raw HTML reaches the browser. Template usage, allure-generator/src/main/javascript/blocks/status-details/status-details.hbs:7,10: Source, plugins/junit-xml-plugin/src/main/java/io/qameta/allure/junitxml/JunitXmlPlugin.java:307-308: These values are read directly from XML attributes with no sanitization. The same pattern exists in TRX, xUnit XML, xctest, and Allure1/2 plugins. Contrast with the fixed helper, linky.js (post-fix) correctly escapes before wrapping in SafeString: PoC Create a malicious JUnit XML test result file: Generate an Allure report: Open the report and navigate to the failed test case: When viewing the test's status details, the <img onerror> payloads execute JavaScript in the viewer's browser. Impact Arbitrary JavaScript execution in the browser of anyone viewing the generated Allure report Cookie theft, session hijacking if the report is served from a domain with active sessions (e.g., CI dashboards) Data exfiltration, the injected script can read the full report content and send it to an attacker-controlled server Attack vectors: A malicious dependency that throws crafted exception messages, a CI pipeline processing test results from untrusted pull requests, or a contributor submitting test files containing XSS payloads Allure reports are commonly hosted on CI/CD platforms (Jenkins, GitLab, GitHub Actions artifacts) where session cookies may be present Recommended Fix Configure AnsiToHtml with escapeForHtml: true to escape HTML entities while preserving ANSI-to-HTML conversion: This is the correct approach because it preserves the ANSI escape sequence → HTML conversion (colored output) while ensuring that any non-ANSI HTML in the input is safely escaped. The alternative of using escapeExpression() on the input would destroy ANSI sequences before they could be converted.
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
CVE-2026-55847 has a CVSS score of 6.1 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (2.39.0). Upgrading removes the vulnerable code path.
maven
io.qameta.allure:allure-generator (<= 2.38.1)io.qameta.allure:allure-generator → 2.39.0 (maven)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-55847 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-55847 is reachable in your applications. Get a demo
Upgrade io.qameta.allure:allure-generator to 2.39.0 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-55847 is a medium-severity cross-site scripting (XSS) vulnerability in io.qameta.allure:allure-generator (maven), affecting versions <= 2.38.1. It is fixed in 2.39.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
CVE-2026-55847 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
io.qameta.allure:allure-generator (maven) versions <= 2.38.1 is affected.
Yes. CVE-2026-55847 is fixed in 2.39.0. Upgrade to this version or later.
Whether CVE-2026-55847 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade io.qameta.allure:allure-generator to 2.39.0 or later.