CVE-2026-55847

MEDIUMPre-NVD 6.16.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (27th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-77688 (ENISA EUVD) · GHSA-gx93-m64w-5m6h (GitHub Security Advisories)Source: ENISA EUVD

6.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
28
EG Risk 28/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity61% × 45%
Impact severity (EG Severity): CVSS 6.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
27th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.1): severity, escalated by confirmed exploitation. This CVE's 6.1 is its impact severity (EG Severity), not escalated.

EG Severity
6.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 19, 2026

Last Modified

September 30, 2026

Advisory Details (4)

Auto-updated Sep 14, 2026
Patch available. Sources: github_release, github, github_pr, github_commit.
GitHub release Patch Available

2.39.0

Patch available: allure-framework/allure2 2.39.0

https://github.com/allure-framework/allure2/releases/tag/2.39.0
GitHub commit

commit 1c5693933f51 (allure-framework/allure2)

Fix landed in allure-framework/allure2 commit 1c5693933f51 — awaiting tagged release

https://github.com/allure-framework/allure2/commit/1c5693933f519e64379f1a14eb3c7beeba7bc7cd
GitHub pull request

fix: sanitize descriptionHtml, add ansi helper escaping

Fix merged in allure-framework/allure2 PR #3296 on 2026-04-01 — awaiting tagged release

https://github.com/allure-framework/allure2/pull/3296
GitHub advisoryMentions a patch (unverified)

Stored XSS via unescaped ANSI helper in Allure report status message/trace rendering · Advisory · allure-framework/allure2 · GitHub

https://github.com/allure-framework/allure2/security/advisories/GHSA-gx93-m64w-5m6h

Vendor Advisories for CVE-2026-55847(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
io.qameta.allure:allure-generator2.0-BETA8 ... 2.9.0 (70 versions)
  • every version up to 2.39.0: fixed in 2.39.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  2. 2026-10-30 10:55 UTCOSV refresh
  3. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  4. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  5. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  6. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  7. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  8. 2026-10-25 14:18 UTCEG score recompute
  9. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  10. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  11. 2026-10-22 21:13 UTCEG score recompute
  12. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  13. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  14. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  15. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  16. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  17. 2026-10-18 03:29 UTCEG score recompute
  18. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  19. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  20. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  21. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  22. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  23. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  24. 2026-10-12 15:55 UTCEG score recompute
  25. 2026-10-11 19:38 UTCEG score recompute
Show 33 more
  1. 2026-10-11 16:53 UTCEG score recompute
  2. 2026-10-11 14:16 UTCEG score recompute
  3. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  4. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  5. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  6. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  7. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  8. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  9. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  10. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  11. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  12. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  13. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  14. 2026-09-30 17:53 UTCEG score recompute
  15. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  16. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  17. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  18. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  19. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  20. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  21. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  22. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  23. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  24. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  25. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  26. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  27. 2026-09-14 20:27 UTCEG score recompute
  28. 2026-09-14 20:16 UTCEG score recompute
  29. 2026-09-14 18:38 UTCEG score recompute
  30. 2026-07-31 00:45 UTCEG score recompute
  31. 2026-07-26 16:47 UTCEG score recompute
  32. 2026-07-23 03:20 UTCEG score recompute
  33. 2026-06-19 21:23 UTCEG score recompute

Related CVEs(same product + same CWE)

Same product

1 shown

Maven:io.qameta.allure:allure-generator

Frequently asked(5)

What is CVE-2026-55847?
CVE-2026-55847 is a medium-severity vulnerability; its CVE record was published on June 19, 2026. 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…
When was the CVE record for CVE-2026-55847 published?
The CVE record for CVE-2026-55847 was published on June 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-55847 actively exploited?
CVE-2026-55847 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55847?
CVE-2026-55847 has a CVSS base score of 6.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55847?
A fix for CVE-2026-55847 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55847 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55847

Explore →

Is Your Infrastructure Affected by CVE-2026-55847?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs