{"items":[{"id":"NVI-00014127","kind":"vulnerability","title":"xmldom: Processing Instruction Target Injection Bypasses requireWellFormed","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-c7q8-3ch8-vqpv","CVE-2026-83616"],"plain_summary":"GitHub lists this reviewed advisory for @xmldom/xmldom, @xmldom/xmldom, xmldom. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-2e4b4005d802d5c03a71c87735b2b111"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.612%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.49297. Missing scores are unknown.","source_id":"sr-2e4b4005d802d5c03a71c87735b2b111"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-4d13409321469773e8ad309c48497bb9","url":"https://github.com/advisories/GHSA-c7q8-3ch8-vqpv","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-c7q8-3ch8-vqpv","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T22:54:12.705Z"},{"id":"sr-2e4b4005d802d5c03a71c87735b2b111","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-83616","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:17:01.143Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4d13409321469773e8ad309c48497bb9"],"technology":"@xmldom/xmldom","known_exclusions":[],"conditions_summary":"## Summary\n\n`Document.createProcessingInstruction()` in `@xmldom/xmldom` performs no validation on the `target` parameter. The `requireWellFormed: true` serializer option validates only for `:` in the target and a case-insensitive `xml` prefix, but does not check for `>` characters. A `>` in the target breaks the processing instruction boundary (``), allowing injection of arbitrary content into the serialized XML output.\n\n## Details\n\n`Document.createProcessingInstruction(target, data)` at `lib/dom.js` around line 2413 accepts any string as the `target` parameter and stores it on the PI node without validation.\n\nDuring serialization, the `requireWellFormed` code path (around line 3286) performs two checks on PI targets:\n\n1. Rejects targets containing `:` (namespace prefix check)\n2. Rejects targets matching `xml` case-insensitively (reserved prefix)\n\nHowever, it does NOT validate that the target conforms to the XML Name production, and critically does NOT check for `>` characters. Since processing instructions are serialized as ``, a `>` in the target prematurely closes the PI, causing the remaining content to be interpreted as document content by any downstream","public_affected_ranges":[">= 0.7.0, <= 0.8.14"]},{"certainty":"source_listed","source_ids":["sr-4d13409321469773e8ad309c48497bb9"],"technology":"@xmldom/xmldom","known_exclusions":[],"conditions_summary":"## Summary\n\n`Document.createProcessingInstruction()` in `@xmldom/xmldom` performs no validation on the `target` parameter. The `requireWellFormed: true` serializer option validates only for `:` in the target and a case-insensitive `xml` prefix, but does not check for `>` characters. A `>` in the target breaks the processing instruction boundary (``), allowing injection of arbitrary content into the serialized XML output.\n\n## Details\n\n`Document.createProcessingInstruction(target, data)` at `lib/dom.js` around line 2413 accepts any string as the `target` parameter and stores it on the PI node without validation.\n\nDuring serialization, the `requireWellFormed` code path (around line 3286) performs two checks on PI targets:\n\n1. Rejects targets containing `:` (namespace prefix check)\n2. Rejects targets matching `xml` case-insensitively (reserved prefix)\n\nHowever, it does NOT validate that the target conforms to the XML Name production, and critically does NOT check for `>` characters. Since processing instructions are serialized as ``, a `>` in the target prematurely closes the PI, causing the remaining content to be interpreted as document content by any downstream","public_affected_ranges":[">= 0.9.0, <= 0.9.11"]},{"certainty":"source_listed","source_ids":["sr-4d13409321469773e8ad309c48497bb9"],"technology":"xmldom","known_exclusions":[],"conditions_summary":"## Summary\n\n`Document.createProcessingInstruction()` in `@xmldom/xmldom` performs no validation on the `target` parameter. The `requireWellFormed: true` serializer option validates only for `:` in the target and a case-insensitive `xml` prefix, but does not check for `>` characters. A `>` in the target breaks the processing instruction boundary (``), allowing injection of arbitrary content into the serialized XML output.\n\n## Details\n\n`Document.createProcessingInstruction(target, data)` at `lib/dom.js` around line 2413 accepts any string as the `target` parameter and stores it on the PI node without validation.\n\nDuring serialization, the `requireWellFormed` code path (around line 3286) performs two checks on PI targets:\n\n1. Rejects targets containing `:` (namespace prefix check)\n2. Rejects targets matching `xml` case-insensitively (reserved prefix)\n\nHowever, it does NOT validate that the target conforms to the XML Name production, and critically does NOT check for `>` characters. Since processing instructions are serialized as ``, a `>` in the target prematurely closes the PI, causing the remaining content to be interpreted as document content by any downstream","public_affected_ranges":["<= 0.6.0"]}],"null_published_at":"2026-11-08T19:53:38.922Z","source_updated_at":"2026-09-08T21:03:31.000Z","source_disclosed_at":"2026-09-08T21:03:28.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-11-01T22:54:12.705Z"},{"id":"NVI-00014127","kind":"vulnerability","title":"xmldom: Processing Instruction Target Injection Bypasses requireWellFormed","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-c7q8-3ch8-vqpv","CVE-2026-83616"],"plain_summary":"GitHub lists this reviewed advisory for @xmldom/xmldom, @xmldom/xmldom, xmldom. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-4d13409321469773e8ad309c48497bb9"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-4d13409321469773e8ad309c48497bb9","url":"https://github.com/advisories/GHSA-c7q8-3ch8-vqpv","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-c7q8-3ch8-vqpv","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T22:54:12.705Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4d13409321469773e8ad309c48497bb9"],"technology":"@xmldom/xmldom","known_exclusions":[],"conditions_summary":"## Summary\n\n`Document.createProcessingInstruction()` in `@xmldom/xmldom` performs no validation on the `target` parameter. The `requireWellFormed: true` serializer option validates only for `:` in the target and a case-insensitive `xml` prefix, but does not check for `>` characters. A `>` in the target breaks the processing instruction boundary (``), allowing injection of arbitrary content into the serialized XML output.\n\n## Details\n\n`Document.createProcessingInstruction(target, data)` at `lib/dom.js` around line 2413 accepts any string as the `target` parameter and stores it on the PI node without validation.\n\nDuring serialization, the `requireWellFormed` code path (around line 3286) performs two checks on PI targets:\n\n1. Rejects targets containing `:` (namespace prefix check)\n2. Rejects targets matching `xml` case-insensitively (reserved prefix)\n\nHowever, it does NOT validate that the target conforms to the XML Name production, and critically does NOT check for `>` characters. Since processing instructions are serialized as ``, a `>` in the target prematurely closes the PI, causing the remaining content to be interpreted as document content by any downstream","public_affected_ranges":[">= 0.7.0, <= 0.8.14"]},{"certainty":"source_listed","source_ids":["sr-4d13409321469773e8ad309c48497bb9"],"technology":"@xmldom/xmldom","known_exclusions":[],"conditions_summary":"## Summary\n\n`Document.createProcessingInstruction()` in `@xmldom/xmldom` performs no validation on the `target` parameter. The `requireWellFormed: true` serializer option validates only for `:` in the target and a case-insensitive `xml` prefix, but does not check for `>` characters. A `>` in the target breaks the processing instruction boundary (``), allowing injection of arbitrary content into the serialized XML output.\n\n## Details\n\n`Document.createProcessingInstruction(target, data)` at `lib/dom.js` around line 2413 accepts any string as the `target` parameter and stores it on the PI node without validation.\n\nDuring serialization, the `requireWellFormed` code path (around line 3286) performs two checks on PI targets:\n\n1. Rejects targets containing `:` (namespace prefix check)\n2. Rejects targets matching `xml` case-insensitively (reserved prefix)\n\nHowever, it does NOT validate that the target conforms to the XML Name production, and critically does NOT check for `>` characters. Since processing instructions are serialized as ``, a `>` in the target prematurely closes the PI, causing the remaining content to be interpreted as document content by any downstream","public_affected_ranges":[">= 0.9.0, <= 0.9.11"]},{"certainty":"source_listed","source_ids":["sr-4d13409321469773e8ad309c48497bb9"],"technology":"xmldom","known_exclusions":[],"conditions_summary":"## Summary\n\n`Document.createProcessingInstruction()` in `@xmldom/xmldom` performs no validation on the `target` parameter. The `requireWellFormed: true` serializer option validates only for `:` in the target and a case-insensitive `xml` prefix, but does not check for `>` characters. A `>` in the target breaks the processing instruction boundary (``), allowing injection of arbitrary content into the serialized XML output.\n\n## Details\n\n`Document.createProcessingInstruction(target, data)` at `lib/dom.js` around line 2413 accepts any string as the `target` parameter and stores it on the PI node without validation.\n\nDuring serialization, the `requireWellFormed` code path (around line 3286) performs two checks on PI targets:\n\n1. Rejects targets containing `:` (namespace prefix check)\n2. Rejects targets matching `xml` case-insensitively (reserved prefix)\n\nHowever, it does NOT validate that the target conforms to the XML Name production, and critically does NOT check for `>` characters. Since processing instructions are serialized as ``, a `>` in the target prematurely closes the PI, causing the remaining content to be interpreted as document content by any downstream","public_affected_ranges":["<= 0.6.0"]}],"null_published_at":"2026-11-02T10:00:37.211Z","source_updated_at":"2026-09-08T21:03:31.000Z","source_disclosed_at":"2026-09-08T21:03:28.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-01T22:54:12.705Z"}],"next_cursor":null,"snapshot_revision":"42594"}