Authentication bypass via unsigned XML acceptance
Published Nov 26, 2025 · Updated Nov 28, 2025
Improper signature verification in XML::Sig 0.27 through 0.67 allows remote attackers to bypass XML trust checks with unsigned documents. The verify() routine returns true when an XML document contains no Signature node, treating the absence of a failed check as success. Any application that trusts this result can accept attacker-modified XML after its signature is removed, including SAML authentication data.
Summary
What happened
Improper signature verification in XML::Sig 0.27 through 0.67 allows remote attackers to bypass XML trust checks with unsigned documents. The verify() routine returns true when an XML document contains no Signature node, treating the absence of a failed check as success. Any application that trusts this result can accept attacker-modified XML after its signature is removed, including SAML authentication data.
The record
- CVE
- CVE-2025-40934
- Published
- Nov 26, 2025
- Updated
- Nov 28, 2025
- Vendor
- Timothy Legge
- Product
- XML::Sig
- Classifications
- CWE-347, CAPEC-115, T1606.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 26, 2025CVE publishedPublication date reported by the CVE source.
- Nov 28, 2025Record 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.27 <0.68
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
- Unsigned XML verification proof of conceptproof 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