Trusted XML manipulation via duplicate ID resolution
Published Aug 3, 2026 · Updated Aug 3, 2026
Signature verification in Timothy Legge XML::Sig before 0.71 allows remote attackers to control trusted XML content via duplicate IDs. The verify() path calls _get_signed_xml(), whose XPath lookup selects the first element matching Reference/@URI without rejecting a second element with the same ID. A signed-first, attacker-supplied-second document passes verification while an application can consume the unsigned duplicate, placing SAML2 Assertion contents under attacker control.
Summary
What happened
Signature verification in Timothy Legge XML::Sig before 0.71 allows remote attackers to control trusted XML content via duplicate IDs. The verify() path calls _get_signed_xml(), whose XPath lookup selects the first element matching Reference/@URI without rejecting a second element with the same ID. A signed-first, attacker-supplied-second document passes verification while an application can consume the unsigned duplicate, placing SAML2 Assertion contents under attacker control.
The record
- CVE
- CVE-2026-9487
- Published
- Aug 3, 2026
- Updated
- Aug 3, 2026
- Vendor
- Timothy Legge
- Product
- XML::Sig
- Classifications
- CWE-347, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 3, 2026CVE publishedPublication date reported by the CVE source.
- Aug 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.71
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Duplicate-ID XML signature-wrapping regression testproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo