← Back
CVE-2026-55847
Cross-Site Scripting (XSS) in io.qameta.allure:allure-generator (CVE-2026-55847)
Summary
cross-site scripting in io.qameta.allure:allure-generator (CVE-2026-55847). Risk of unauthorized operations or information disclosure. Exploitable via ``ansi.js``. Mitigation: upgrade to `2.39.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-55847** has been found in io.qameta.allure:allure-generator.
Attackers can target a specific entry point like ``ansi.js`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade io.qameta.allure:allure-generator to **2.39.0** or later.
If unsure, ask your IT team or search "io.qameta.allure:allure-generator CVE-2026-55847" on the vendor's site.
CVE-2026-55847 (io.qameta.allure:allure-generator) — CWE-79 /
Attack surface: `ansi.js` / `statusMessage` / `statusTrace` / `SafeString`
Patched: `2.39.0` — apply immediately
Workaround: set escapeForHtml: true
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Cross-site scripting (XSS)** (CWE-79) exists in io.qameta.allure:allure-generator. Attackers reach the vulnerable code path via ``ansi.js`` without authentication.
📍 Affected scope
io.qameta.allure:allure-generator — . Attack surface: `ansi.js` / `statusMessage` / `statusTrace` / `SafeString`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.39.0**.
🛡️ Workaround
Workaround: set escapeForHtml: true
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'io.qameta.allure:allure-generator' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'io.qameta.allure:allure-generator' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `io.qameta.allure:allure-generator` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
set escapeForHtml: trueパッチが適用されるまでの応急処置として、set escapeForHtml: true を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade io.qameta.allure:allure-generator to 2.39.0ステージング環境で 2.39.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
io.qameta.allure:allure-generator
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.39.0"}]}]