CVEPublished 2026-09-01Modified 2026-09-080 articles on news5 live referencesNVD data

CVE-2026-83606

Vulnerability data via NVD (ingested)

CVSS v3.1
EPSS percentile
22
Exploit Prediction Scoring System · top 78% of all CVEs
Description

xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. From 0.9.0-beta.9 until 0.9.11, the processing-instruction production in lib/grammar.js lets the greedy S+ separator and lazy Char*? data group repeatedly repartition a long whitespace tail when the required closing ?> is absent. Both parsePI and parseProcessingInstruction apply the expression to the entire remaining source, causing quadratic backtracking during DOMParser.parseFromString() under default options and allowing a small unauthenticated XML input to stall the Node.js event loop. This issue is fixed in @xmldom/xmldom version 0.9.11.

Timeline
Published 2026-09-01
Modified 2026-09-08

External references

Search for exposed instances

Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).

More intel sources (5)

Known PoCs on GitHub

No public proof-of-concept repositories found for CVE-2026-83606 on GitHub.
We haven't classified any articles referencing CVE-2026-83606 yet. The external references above still apply.