CVE-2026-84371

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreMEDIUM confidence

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

Score 5.4 from GitHub Security Advisory (severity: MODERATE) published 2026-09-01. A secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-69654 (ENISA EUVD) · GHSA-g8qq-57p8-ggw5 (GitHub Security Advisories)Source: ENISA EUVD

5.4EG
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: 5.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

ApostropheCMS is an open-source Node.js content management system, and sanitize-html provides a simple HTML sanitizer with a clear API. From version 1.9.0 until version 2.17.7, packages/sanitize-html/index.js validates an animation value attribute as one flat URL and does not recognize that attributeName selecting href or xlink:href gives the sibling values, from, to, or by attribute SVG SMIL URL semantics. In configurations that allow the animate, animateColor, animateMotion, animateTransform, or set elements, a values list can begin with a safe fragment and contain a later executable destination that survives allowedSchemesAppliedToAttributes checking. When the sanitized SVG is rendered, the browser can copy that later destination into the live link, and a victim who activates the link can execute script in the application's origin. This issue is fixed in version 2.17.7.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/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)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 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
22nd
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 (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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, and whom BOD 26-04 binds: 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.

The score's inputs: 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

September 1, 2026

Last Modified

September 9, 2026

Advisory Details (5)

Auto-updated Sep 1, 2026
Patch available. Sources: github, github_pr, github_commit.
Web page

apostrophe/packages/sanitize-html/CHANGELOG.md at main · apostrophecms/apostrophe · GitHub

https://github.com/apostrophecms/apostrophe/blob/main/packages/sanitize-html/CHANGELOG.md
GitHub commit

commit 38ff1106c817 (apostrophecms/apostrophe)

Fix landed in apostrophecms/apostrophe commit 38ff1106c817 — awaiting tagged release

https://github.com/apostrophecms/apostrophe/commit/38ff1106c8176b16c2da9872acd9b449adcbb949
GitHub commit

commit 1135516a1a4a (apostrophecms/apostrophe)

Fix landed in apostrophecms/apostrophe commit 1135516a1a4a — awaiting tagged release

https://github.com/apostrophecms/apostrophe/commit/1135516a1a4a8f9638641c460488a43d8af20081
GitHub pull request

Stable reconciliation q2 m3 2026

Fix merged in apostrophecms/apostrophe PR #5552 on 2026-08-12 — awaiting tagged release

https://github.com/apostrophecms/apostrophe/pull/5552
GitHub advisoryMentions a patch (unverified)

Stored XSS via SVG SMIL URI-list scheme-policy bypass · Advisory · apostrophecms/apostrophe · GitHub

https://github.com/apostrophecms/apostrophe/security/advisories/GHSA-g8qq-57p8-ggw5

Vendor Advisories for CVE-2026-84371(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmsanitize-html @ 2.17.7 (fixes >= 1.9.0, <= 2.17.6)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
sanitize-html—
  • 1.9.0 up to 2.17.7: fixed in 2.17.7
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 46× 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.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 99 are merged into the row they repeat.

  1. 2026-11-01 07:38 UTCGHSA enrichmentGHSA-g8qq-57p8-ggw5 · GitHub severity MODERATE · GitHub CVSS 5.4
  2. 2026-11-01 07:38 UTCEG score recompute
  3. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  4. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  5. 2026-10-30 00:55 UTCOSV refresh
  6. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  7. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  8. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  9. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  10. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  11. 2026-10-25 13:56 UTCEG score recompute
  12. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  13. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  14. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  15. 2026-10-22 13:14 UTCEG score recompute
  16. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  17. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  18. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  19. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  20. 2026-10-18 03:06 UTCEG score recompute
  21. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  22. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  23. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  24. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  25. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 20th percentile
Show 72 more
  1. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-10-12 14:53 UTCEG score recompute
  3. 2026-10-11 19:18 UTCEG score recompute
  4. 2026-10-11 16:35 UTCEG score recompute
  5. 2026-10-11 13:52 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  8. 2026-10-10 05:04 UTCEG score recompute
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  10. 2026-10-09 03:12 UTCEG score recompute
  11. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  12. 2026-10-08 02:18 UTCEG score recompute
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  14. 2026-10-07 01:25 UTCEG score recompute
  15. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  16. 2026-10-06 00:32 UTCEG score recompute
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  18. 2026-10-04 23:32 UTCEG score recompute
  19. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  20. 2026-10-03 22:38 UTCEG score recompute
  21. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  22. 2026-10-02 21:30 UTCEG score recompute
  23. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  24. 2026-10-01 20:35 UTCEG score recompute
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  26. 2026-09-30 19:28 UTCEG score recompute
  27. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  28. 2026-09-29 16:07 UTCEG score recompute
  29. 2026-09-28 15:13 UTCEG score recompute
  30. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  31. 2026-09-27 14:20 UTCEG score recompute
  32. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  33. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  34. 2026-09-26 12:50 UTCEG score recompute
  35. 2026-09-25 11:54 UTCEG score recompute
  36. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  37. 2026-09-24 11:01 UTCEG score recompute
  38. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  39. 2026-09-23 10:08 UTCEG score recompute
  40. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  41. 2026-09-22 09:14 UTCEG score recompute
  42. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  43. 2026-09-21 08:07 UTCEG score recompute
  44. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  45. 2026-09-20 07:14 UTCEG score recompute
  46. 2026-09-19 05:31 UTCEG score recompute
  47. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  48. 2026-09-18 04:38 UTCEG score recompute
  49. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  50. 2026-09-17 03:45 UTCEG score recompute
  51. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  52. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  53. 2026-09-16 02:52 UTCEG score recompute
  54. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  55. 2026-09-14 01:04 UTCEG score recompute
  56. 2026-09-13 00:10 UTCEG score recompute
  57. 2026-09-11 23:17 UTCEG score recompute
  58. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  59. 2026-09-10 22:04 UTCEG score recompute
  60. 2026-09-07 20:52 UTCEG score recompute
  61. 2026-09-06 19:59 UTCEG score recompute
  62. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  63. 2026-09-05 19:05 UTCEG score recompute
  64. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  65. 2026-09-04 18:11 UTCEG score recompute
  66. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  67. 2026-09-03 17:16 UTCEG score recompute
  68. 2026-09-02 16:20 UTCEG score recompute
  69. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  70. 2026-09-01 21:26 UTCEG score recompute
  71. 2026-09-01 20:53 UTCEG score recomputeFirst assessed: 5.4 MEDIUM
  72. 2026-09-01 20:52 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-84371?
CVE-2026-84371 is a medium-severity vulnerability; its CVE record was published on September 1, 2026. ApostropheCMS is an open-source Node.js content management system, and sanitize-html provides a simple HTML sanitizer with a clear API. From version 1.9.0 until version 2.17.7, packages/sanitize-html/index.js validates an animation value attribute as one flat URL and does not recognize that…
When was the CVE record for CVE-2026-84371 published?
The CVE record for CVE-2026-84371 was published on September 1, 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 9, 2026; the record at its source may have been updated since.
Is CVE-2026-84371 actively exploited?
CVE-2026-84371 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-84371?
CVE-2026-84371 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-84371?
A fix for CVE-2026-84371 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-84371 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-84371

Explore →

Is Your Infrastructure Affected by CVE-2026-84371?

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

Book a Demo →Browse All CVEs