Loading vulnerability…
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.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
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.Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A denial-of-service vulnerability in the fast-xml-parser component where specially crafted XML input (numeric entity handling leading to a RangeError/uncaught exception) can crash or disrupt the service.
A fast-xml-parser vulnerability where specially crafted input can trigger a RangeError (numeric entity handling) leading to remote denial of service (DoS).
A fast-xml-parser vulnerability that can be triggered remotely to cause denial of service via an uncaught exception (RangeError) when processing numeric entities.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.