Bug 2528036 - CVE-2026-83616 onnxruntime: xmldom: XML Structure Injection via Unvalidated Processing Instruction Targets [fedora-all]
Summary: CVE-2026-83616 onnxruntime: xmldom: XML Structure Injection via Unvalidated P...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: onnxruntime
Version: rawhide
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Diego Herrera
QA Contact:
URL:
Whiteboard: {"flaws": ["1f2a68c8-1966-4210-ab3d-2...
Depends On:
Blocks: CVE-2026-83616
TreeView+ depends on / blocked
 
Reported: 2026-09-03 13:59 UTC by Joel Chamberlain
Modified: 2026-09-23 21:45 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:
fedora-admin-xmlrpc: mirror+


Attachments (Terms of Use)

Description Joel Chamberlain 2026-09-03 13:59:47 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

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 <?target data?>, 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.

Comment 1 Fedora Admin user for bugzilla script actions 2026-09-23 21:45:01 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.


Note You need to log in before you can comment on or make changes to this bug.