What is CVE-2026-83615?

CVE-2026-83615 is a high-severity allocation of resources without limits or throttling vulnerability in @xmldom/xmldom (npm), affecting versions >= 0.7.0, <= 0.8.14. It is fixed in 0.8.15, 0.9.12. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.

Which packages are affected by CVE-2026-83615?

@xmldom/xmldom (npm) versions >= 0.7.0, = 0.1.5, <= 0.6.0.

Is there a fix for CVE-2026-83615?

Yes. CVE-2026-83615 is fixed in 0.8.15, 0.9.12. Upgrade to this version or later.

Is CVE-2026-83615 exploitable, and should I be worried?

Whether CVE-2026-83615 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-83615 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-83615 in @xmldom/xmldom

Q: Which packages are affected by CVE-2026-83615?

@xmldom/xmldom (npm) versions >= 0.7.0, = 0.1.5, <= 0.6.0.

Q: Is there a fix for CVE-2026-83615?

Yes. CVE-2026-83615 is fixed in 0.8.15, 0.9.12. Upgrade to this version or later.

Q: Is CVE-2026-83615 exploitable, and should I be worried?

Whether CVE-2026-83615 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-83615 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-83615?

Upgrade: @xmldom/xmldom to 0.8.15 or later, @xmldom/xmldom to 0.9.12 or later.

Summary

xmldom: Quadratic-memory consumption

Impact

Unauthenticated denial of service against any service that parses attacker-influenced XML with
xmldom under default options. A single sub-megabyte request drives multi-gigabyte peak memory and
can OOM-crash the process before any application-level validation (e.g. schema checks or a SAML
signature verification) runs. The payload is a plain namespace-nesting document and highly
compressible, so it is effective over compressed transports (e.g. an HTTP-Redirect / DEFLATE
binding, not only POST bindings).

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

Affected versions

@xmldom/xmldom (>= 0.7.0, <= 0.8.14) @xmldom/xmldom (>= 0.9.0, <= 0.9.11) xmldom (>= 0.1.5, <= 0.6.0)

Security releases

@xmldom/xmldom → 0.8.15 (npm) @xmldom/xmldom → 0.9.12 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

@xmldom/xmldom to 0.8.15 or later; @xmldom/xmldom to 0.9.12 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-83615? CVE-2026-83615 is a high-severity allocation of resources without limits or throttling vulnerability in @xmldom/xmldom (npm), affecting versions >= 0.7.0, <= 0.8.14. It is fixed in 0.8.15, 0.9.12. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
Which packages are affected by CVE-2026-83615?
- @xmldom/xmldom (npm) (versions >= 0.7.0, <= 0.8.14)
- xmldom (npm) (versions >= 0.1.5, <= 0.6.0)
Is there a fix for CVE-2026-83615? Yes. CVE-2026-83615 is fixed in 0.8.15, 0.9.12. Upgrade to this version or later.
Is CVE-2026-83615 exploitable, and should I be worried? Whether CVE-2026-83615 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-83615 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-83615?
- Upgrade @xmldom/xmldom to 0.8.15 or later
- Upgrade @xmldom/xmldom to 0.9.12 or later