{"answers":{"affected":"2 open source packages ship an affected version, including io.qameta.allure:allure-generator.","exploited":"There is no known exploitation of CVE-2026-55847 in the wild and no public exploit code.","fix":"Upgrade io.qameta.allure:allure-generator to 2.39.0 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-55847 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: There is no known exploitation of CVE-2026-55847 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.qameta.allure:allure-generator (Maven): affected all versions; fixed in 2.39.0\n- io.qameta.allure:allure-generator (Maven): affected all versions; fixed in 2.39.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-55847/ (Markdown: https://insights.sbomify.com/CVE-2026-55847/index.md)","id":"CVE-2026-55847","markdown":"https://insights.sbomify.com/CVE-2026-55847/index.md","name":"CVE-2026-55847","record":{"aliases":["GHSA-gx93-m64w-5m6h","UBUNTU-CVE-2026-55847"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Allure Report","requires_auth":"none","summary":"Attackers can inject malicious scripts into Allure reports via crafted test results, leading to arbitrary JavaScript execution when users view the report.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Allure: Stored XSS via unescaped ANSI helper in Allure report status message/trace rendering","id":"CVE-2026-55847","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"mapfish-print: XXE on MapFish Print allows reading arbitrary files of certain types","id":"CVE-2026-55848"},"packages":[{"ecosystem":"Maven","fixed":["2.39.0"],"introduced":["0"],"last_affected":[],"package":"io.qameta.allure:allure-generator","purl":null,"source":"GHSA-gx93-m64w-5m6h"},{"ecosystem":"Maven","fixed":["2.39.0"],"introduced":["0"],"last_affected":[],"package":"io.qameta.allure:allure-generator","purl":"pkg:maven/io.qameta.allure/allure-generator","source":"GHSA-gx93-m64w-5m6h"}],"prev":{"headline":"Allure: Path Traversal in Allure Report HTTP Server Allows Arbitrary File Read","id":"CVE-2026-55846"},"products":["allure-generator","allure2"],"published":"2026-09-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-14","vendors":["allure-framework","io.qameta.allure"]},"summary":"Attackers can inject malicious scripts into Allure reports via crafted test results, leading to arbitrary JavaScript execution when users view the report.","url":"https://insights.sbomify.com/CVE-2026-55847/"}