ubuntu-cve-2026-83616
Vulnerability from osv_ubuntu
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. Prior to @xmldom/xmldom versions 0.8.15 and 0.9.12, and in xmldom version 0.6.0 and earlier, Document.createProcessingInstruction(target, data) in lib/dom.js accepts an unvalidated target, while the requireWellFormed: true serializer checks only for a colon and the reserved case-insensitive xml name on 0.9.x and performs no target check on 0.8.x. Because serialization emits , a target containing >, ?, whitespace, or another invalid XML-name character can break the processing-instruction boundary and inject XML structure. This issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fixed version is available for xmldom.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-xmldom",
"binary_version": "0.1.27+ds-1+deb10u2build0.20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "node-xmldom",
"purl": "pkg:deb/ubuntu/node-xmldom@0.1.27+ds-1+deb10u2build0.20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.1.27+ds-1",
"0.1.27+ds-1+deb10u2build0.20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-xmldom",
"binary_version": "0.7.5-1ubuntu0.22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "node-xmldom",
"purl": "pkg:deb/ubuntu/node-xmldom@0.7.5-1ubuntu0.22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.5.0-1",
"0.7.3-1",
"0.7.5-1",
"0.7.5-1ubuntu0.22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-xmldom",
"binary_version": "0.8.6-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "node-xmldom",
"purl": "pkg:deb/ubuntu/node-xmldom@0.8.6-1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.8.6-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-xmldom",
"binary_version": "0.9.8-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "node-xmldom",
"purl": "pkg:deb/ubuntu/node-xmldom@0.9.8-2?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.9.6-1",
"0.9.8-1",
"0.9.8-2"
]
}
],
"aliases": [],
"details": "xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. Prior to @xmldom/xmldom versions 0.8.15 and 0.9.12, and in xmldom version 0.6.0 and earlier, Document.createProcessingInstruction(target, data) in lib/dom.js accepts an unvalidated target, while the requireWellFormed: true serializer checks only for a colon and the reserved case-insensitive xml name on 0.9.x and performs no target check on 0.8.x. Because serialization emits \u003c?target data?\u003e, a target containing \u003e, ?, whitespace, or another invalid XML-name character can break the processing-instruction boundary and inject XML structure. This issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fixed version is available for xmldom.",
"id": "UBUNTU-CVE-2026-83616",
"modified": "2026-09-16T11:43:10Z",
"published": "2026-09-01T15:17:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-83616"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-83616"
},
{
"type": "REPORT",
"url": "https://github.com/xmldom/xmldom/security/advisories/GHSA-c7q8-3ch8-vqpv"
},
{
"type": "REPORT",
"url": "https://github.com/xmldom/xmldom/pull/1071"
},
{
"type": "REPORT",
"url": "https://github.com/xmldom/xmldom/pull/1072"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-83616"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.