Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
HighPublic exploit

DoS via uncaught RangeError in fast-xml-parser numeric entity processing

IdentifiersCVE-2026-25128CWE-248· Uncaught Exception

In fast-xml-parser versions 5.0.9 through 5.3.3, parsing XML containing out-of-range numeric character references (e.g., � or �) triggers a RangeError during numeric entity processing (e.g., via String.fromCodePoint()), and the exception is not caught. As a result, applications that parse untrusted XML with entity processing enabled can crash due to an uncaught exception. Version 5.3.4 fixes the issue.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Remote Denial of Service (process crash): a crafted XML payload with out-of-range numeric entities causes an uncaught RangeError during parsing, terminating the Node.js process (or otherwise crashing the hosting application) when processing untrusted XML input.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible: avoid parsing untrusted XML; disable entity processing features where possible (e.g., do not enable processEntities/htmlEntities unless required); wrap parsing in try/catch (or equivalent error handling) to prevent process termination and return a controlled error; and pre-validate/reject numeric entities outside the Unicode scalar range (0..0x10FFFF) before invoking the parser.

Remediation

Patch, then assume compromise.

Upgrade fast-xml-parser to 5.3.4 or later, which fixes the out-of-range numeric entity handling to prevent the uncaught RangeError crash condition.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Natural IntelligenceFast-Xml-Parserapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity9

Community discussion across Reddit, Mastodon, and other social sources.