CVE-2026-18568
HIGHDescription
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 `id_attr` 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 `id_attr`. 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 `cert_text` 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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Exploit Intelligence
EPSS data unavailable for this CVE.
References
Related Vulnerabilities
Other CWE-347 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2018-16042 | Medium | 6.5 | 82% | - | - |
| CVE-2025-25292 | Critical | 9.8 | 64% | - | Fix |
| CVE-2025-59718 | Critical | 9.8 | 63% | KEV | Fix |
| CVE-2021-22160 | Critical | 9.8 | 53% | - | Fix |
| CVE-2013-3900 | Medium | 5.5 | 45% | KEV | - |
| CVE-2018-0114 | High | 7.5 | 43% | - | Fix |
Common questions
How do I fix CVE-2026-18568?
No published fix for CVE-2026-18568 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
How severe is CVE-2026-18568?
CVE-2026-18568 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-18568
Markdown
[](https://tridentstack.com/cve/CVE-2026-18568)HTML
<a href="https://tridentstack.com/cve/CVE-2026-18568"><img src="https://tridentstack.com/cve/badge/CVE-2026-18568.svg" alt="CVE-2026-18568"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-03.