CVE-2026-18568: CWE-347 Improper Verification of Cryptographic Signature in TIMLEGGE XML::Sig
XML::Sig versions 0.29 up to but not including 0.72 for Perl contain a vulnerability that allows signature verification to be bypassed. The verify function can return true even when no cryptographic signature or digest check is performed if all Signature elements are skipped due to certain conditions. This means untrusted XML documents may be accepted as valid without proper signature verification. Versions up to 0.28 are not affected as they use a different verification method.
AI Analysis
Technical Summary
The vulnerability in XML::Sig (CVE-2026-18568) arises from improper verification of cryptographic signatures (CWE-347). The verify function in lib/XML/Sig.pm counts Signature elements and iterates over them, but certain conditions cause the loop to skip signature checks without recording any verification. If all signatures are skipped—such as when Reference URIs do not resolve to elements or do not match requested IDs—the function returns true unconditionally, indicating successful verification despite no cryptographic validation. This flaw allows attackers to bypass signature verification when untrusted XML is processed. The issue affects versions from 0.29 up to but not including 0.72. Versions 0.28 and earlier are unaffected due to a different verification implementation.
Potential Impact
An attacker can craft XML documents that bypass signature verification, causing the verify function to return true without any cryptographic checks. This can lead to acceptance of forged or tampered XML data as valid, potentially undermining trust in signed XML documents. The vulnerability affects applications relying on XML::Sig for signature validation, exposing them to risks of data integrity and authenticity compromise.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should avoid using affected versions (0.29 up to but not including 0.72) of XML::Sig for signature verification on untrusted XML data. Downgrading to version 0.28 or earlier, which uses a different verification method not affected by this issue, may be considered as a temporary mitigation. Monitor vendor communications for official patches or updates.
CVE-2026-18568: CWE-347 Improper Verification of Cryptographic Signature in TIMLEGGE XML::Sig
Description
XML::Sig versions 0.29 up to but not including 0.72 for Perl contain a vulnerability that allows signature verification to be bypassed. The verify function can return true even when no cryptographic signature or digest check is performed if all Signature elements are skipped due to certain conditions. This means untrusted XML documents may be accepted as valid without proper signature verification. Versions up to 0.28 are not affected as they use a different verification method.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in XML::Sig (CVE-2026-18568) arises from improper verification of cryptographic signatures (CWE-347). The verify function in lib/XML/Sig.pm counts Signature elements and iterates over them, but certain conditions cause the loop to skip signature checks without recording any verification. If all signatures are skipped—such as when Reference URIs do not resolve to elements or do not match requested IDs—the function returns true unconditionally, indicating successful verification despite no cryptographic validation. This flaw allows attackers to bypass signature verification when untrusted XML is processed. The issue affects versions from 0.29 up to but not including 0.72. Versions 0.28 and earlier are unaffected due to a different verification implementation.
Potential Impact
An attacker can craft XML documents that bypass signature verification, causing the verify function to return true without any cryptographic checks. This can lead to acceptance of forged or tampered XML data as valid, potentially undermining trust in signed XML documents. The vulnerability affects applications relying on XML::Sig for signature validation, exposing them to risks of data integrity and authenticity compromise.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should avoid using affected versions (0.29 up to but not including 0.72) of XML::Sig for signature verification on untrusted XML data. Downgrading to version 0.28 or earlier, which uses a different verification method not affected by this issue, may be considered as a temporary mitigation. Monitor vendor communications for official patches or updates.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- CPANSec
- Date Reserved
- 2026-08-02T00:59:21.745Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a70b4e4bf32cb7a34cc8d21
Added to database: 08/03/2026, 15:33:56 UTC
Last enriched: 08/03/2026, 15:55:54 UTC
Last updated: 08/03/2026, 16:28:00 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.