CVE-2026-25128

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 56% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

fast-xml-parser allows users to validate XML, parse XML to JS object, or build XML from JS object without C/C++ based libraries and no callback. In versions 5.0.9 through 5.3.3, a RangeError vulnerability exists in the numeric entity processing of fast-xml-parser when parsing XML with out-of-range entity code points (e.g., � or �). This causes the parser to throw an uncaught exception, crashing any application that processes untrusted XML input. Version 5.3.4 fixes the issue.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

January 30, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 6, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

RangeError DoS Numeric Entities Bug · Advisory · NaturalIntelligence/fast-xml-parser · GitHub

https://github.com/NaturalIntelligence/fast-xml-parser/security/advisories/GHSA-37qj-frw5-hhjh
github_release Patch Available

fix: handle HTML numeric and hex entities when out of range

Patch available: NaturalIntelligence/fast-xml-parser v5.3.4

https://github.com/NaturalIntelligence/fast-xml-parser/releases/tag/v5.3.4
github_commit Patch Available

commit 4e387f61c4a5 (NaturalIntelligence/fast-xml-parser)

Patch available: NaturalIntelligence/fast-xml-parser v5.3.4 (contains commit 4e387f61c4a5)

https://github.com/NaturalIntelligence/fast-xml-parser/commit/4e387f61c4a5cef792f6a2f42467013290bf95dc

Vendor Advisories for CVE-2026-25128(6)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatsatellite/iop-host-inventory-frontend-rhel9:17859227642026-08-06redhat
redhatodf4/rook-ceph-rhel9-operator:17836853752026-07-20redhat
redhatodf4/rook-ceph-rhel9-operator:17836692192026-07-16redhat
redhatodf4/rook-ceph-rhel9-operator:17815574962026-06-16redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17755941192026-04-08redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17755942842026-04-08redhat

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 rangeFixed inDependents
fast-xml-parser—5.3.4—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 152 total refreshes for this CVE.

  1. 2026-08-30 19:17 UTCEPSS rescore
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-27 14:25 UTCEPSS rescore
  5. 2026-08-26 14:46 UTCEPSS rescore
  6. 2026-08-25 13:48 UTCEPSS rescore
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-19 17:03 UTCEPSS rescore
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 01:30 UTCEPSS rescore
  16. 2026-08-14 23:56 UTCVendor advisory
  17. 2026-08-14 11:52 UTCEG score recompute
  18. 2026-08-14 11:52 UTCVendor advisory
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-13 03:59 UTCEG score recompute
  21. 2026-08-13 03:59 UTCVendor advisory
  22. 2026-08-12 13:50 UTCEPSS rescore
  23. 2026-08-11 13:42 UTCEPSS rescore
  24. 2026-08-11 00:00 UTCEPSS rescore
  25. 2026-08-10 10:09 UTCVendor advisory
Show 75 more
  1. 2026-08-09 16:22 UTCEG score recompute
  2. 2026-08-09 16:22 UTCVendor advisory
  3. 2026-08-09 13:46 UTCEPSS rescore
  4. 2026-08-08 16:37 UTCEPSS rescore
  5. 2026-08-07 23:09 UTCEG score recompute
  6. 2026-08-07 23:09 UTCVendor advisory
  7. 2026-08-06 13:46 UTCEPSS rescore
  8. 2026-08-06 04:40 UTCEG score recompute
  9. 2026-08-06 04:40 UTCVendor advisory
  10. 2026-08-05 19:17 UTCEPSS rescore
  11. 2026-08-04 15:10 UTCEPSS rescore
  12. 2026-08-03 10:36 UTCEPSS rescore
  13. 2026-08-02 21:50 UTCEG score recompute
  14. 2026-08-02 21:50 UTCVendor advisory
  15. 2026-08-02 02:26 UTCEPSS rescore
  16. 2026-08-01 04:16 UTCEPSS rescore
  17. 2026-07-31 04:46 UTCOSV refresh
  18. 2026-07-30 16:27 UTCEPSS rescore
  19. 2026-07-30 01:30 UTCEPSS rescore
  20. 2026-07-27 14:13 UTCEPSS rescore
  21. 2026-07-26 14:54 UTCEPSS rescore
  22. 2026-07-26 14:54 UTCEPSS rescore
  23. 2026-07-25 14:17 UTCEPSS rescore
  24. 2026-07-25 14:17 UTCEPSS rescore
  25. 2026-07-24 14:17 UTCEPSS rescore
  26. 2026-07-23 14:18 UTCEPSS rescore
  27. 2026-07-23 14:18 UTCEPSS rescore
  28. 2026-07-23 03:07 UTCEG score recompute
  29. 2026-07-22 14:08 UTCEPSS rescore
  30. 2026-07-21 15:24 UTCEPSS rescore
  31. 2026-07-21 15:24 UTCEPSS rescore
  32. 2026-07-20 17:08 UTCEPSS rescore
  33. 2026-07-19 14:31 UTCEPSS rescore
  34. 2026-07-19 14:31 UTCEPSS rescore
  35. 2026-07-19 02:29 UTCEPSS rescore
  36. 2026-07-19 02:28 UTCEPSS rescore
  37. 2026-07-18 10:04 UTCEPSS rescore
  38. 2026-07-18 10:04 UTCEPSS rescore
  39. 2026-07-16 17:03 UTCEPSS rescore
  40. 2026-07-16 17:03 UTCEPSS rescore
  41. 2026-07-15 16:57 UTCEPSS rescore
  42. 2026-07-15 16:57 UTCEPSS rescore
  43. 2026-07-15 02:00 UTCEPSS rescore
  44. 2026-07-15 02:00 UTCEPSS rescore
  45. 2026-07-13 22:30 UTCEPSS rescore
  46. 2026-07-13 12:37 UTCOSV refresh
  47. 2026-07-13 06:13 UTCEPSS rescore
  48. 2026-07-13 06:13 UTCEPSS rescore
  49. 2026-07-12 05:46 UTCEPSS rescore
  50. 2026-07-12 05:46 UTCEPSS rescore
  51. 2026-07-11 08:27 UTCEPSS rescore
  52. 2026-07-09 19:10 UTCEPSS rescore
  53. 2026-07-08 15:15 UTCEPSS rescore
  54. 2026-07-08 15:15 UTCEPSS rescore
  55. 2026-07-07 13:46 UTCEPSS rescore
  56. 2026-07-06 16:27 UTCEPSS rescore
  57. 2026-07-06 16:27 UTCEPSS rescore
  58. 2026-07-06 02:23 UTCEPSS rescore
  59. 2026-07-06 02:23 UTCEPSS rescore
  60. 2026-07-05 02:30 UTCEPSS rescore
  61. 2026-07-04 06:31 UTCEPSS rescore
  62. 2026-07-04 06:31 UTCEPSS rescore
  63. 2026-07-01 15:06 UTCEPSS rescore
  64. 2026-07-01 15:06 UTCEPSS rescore
  65. 2026-06-30 23:22 UTCEPSS rescore
  66. 2026-06-30 23:22 UTCEPSS rescore
  67. 2026-06-29 14:06 UTCEPSS rescore
  68. 2026-06-28 14:07 UTCEPSS rescore
  69. 2026-06-28 14:07 UTCEPSS rescore
  70. 2026-06-28 04:56 UTCEPSS rescore
  71. 2026-06-28 04:56 UTCEPSS rescore
  72. 2026-06-27 03:08 UTCEPSS rescore
  73. 2026-06-25 13:49 UTCEPSS rescore
  74. 2026-06-25 13:49 UTCEPSS rescore
  75. 2026-06-25 07:31 UTCOSV refresh

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-25128?
CVE-2026-25128 is a high vulnerability published on January 30, 2026. fast-xml-parser allows users to validate XML, parse XML to JS object, or build XML from JS object without C/C++ based libraries and no callback. In versions 5.0.9 through 5.3.3, a RangeError vulnerability exists in the numeric entity processing of fast-xml-parser when parsing XML with out-of-range…
When was CVE-2026-25128 disclosed?
CVE-2026-25128 was first published in the National Vulnerability Database on January 30, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-25128 actively exploited?
CVE-2026-25128 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 55.2% of all scored CVEs.
What is the CVSS score of CVE-2026-25128?
CVE-2026-25128 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-25128?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25128, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-25128?

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

Start Free Scan →Browse All CVEs