CVE-2026-18568: XML::Sig versions from 0.29 before 0.72 for Perl allow signature verification bypass because verify returns true when every signature was skipped before any cryptographic check

Published Aug 3, 2026
·
Updated

XML::Sig versions from 0.29 before 0.72 for Perl allow signature verification bypass because verify returns true when every signature was skipped before any cryptographic check.

verify in lib/XML/Sig.pm counts the //dsig:Signature elements into $numsigs and iterates over them, but two paths reach next before any digest or key check runs: a SignedInfo/Reference/@URI that resolves to no element while $numsigs is greater than 1, and, when idattr is set, a reference that does not match the requested ID. The loop records nothing about what it checked, so when every signature takes one of those paths control reaches the unconditional return 1 that ends verify. Two Signature elements whose Reference URI names an ID that no element carries is enough, as is one such element combined with idattr.

Any caller that passes untrusted XML to verify can receive a true return for a document in which no digest and no signature value was checked; a cert or certtext trust anchor does not change this, because no key check runs. Versions up to 0.28 use an XML::XPath based verify that has no such skip and are not affected.

Affected Software

1 affected component
Perl XML::Sig>0.29<0.72

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade XML::Sig to a version that resolves this vulnerability.

    Fixed in 0.72
  2. Configuration

    If using the Perl XML::Sig verify logic, avoid setting id_attr (in lib/XML/Sig.pm) so that references with non-matching IDs do not take the path where cryptographic digest/key checks are skipped and control can reach the unconditional return 1.

    XML::Sig (verify in lib/XML/Sig.pm) id_attr = unset / not set

Event History

Aug 3, 2026
CVE Published
via MITRE·02:38 PM
Data Sourced
via MITRE·02:38 PM
RemedyDescriptionWeakness
Data Sourced
via NVD·04:16 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-18568?

The severity of CVE-2026-18568 is rated as 71 on the risk scale.

2

How do I fix CVE-2026-18568?

To fix CVE-2026-18568, you should upgrade XML::Sig to version 0.72 or later.

3

What does CVE-2026-18568 affect?

CVE-2026-18568 affects XML::Sig versions from 0.29 before 0.72 for Perl.

4

What is the impact of CVE-2026-18568?

The impact of CVE-2026-18568 is a signature verification bypass that can result in improper validation of XML signatures.

5

Who is affected by CVE-2026-18568?

Any user or developer utilizing vulnerable versions of the XML::Sig module in Perl is affected by CVE-2026-18568.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203