CVE-2026-18568

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-03. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

August 3, 2026

Last Modified

August 5, 2026

Vendor Advisories for CVE-2026-18568(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 25× in last 7d / 72× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 05:13 UTCEG score recompute
  2. 2026-08-21 05:13 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 16:22 UTCGHSA enrichment
  5. 2026-08-20 03:31 UTCEG score recompute
  6. 2026-08-20 03:31 UTCGHSA enrichment
  7. 2026-08-19 17:03 UTCEPSS rescore
  8. 2026-08-19 14:39 UTCGHSA enrichment
  9. 2026-08-19 01:43 UTCEG score recompute
  10. 2026-08-19 01:43 UTCGHSA enrichment
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-18 12:51 UTCGHSA enrichment
  13. 2026-08-17 23:13 UTCGHSA enrichment
  14. 2026-08-17 10:21 UTCGHSA enrichment
  15. 2026-08-16 21:30 UTCEG score recompute
  16. 2026-08-16 21:30 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 08:38 UTCEG score recompute
  19. 2026-08-16 08:38 UTCGHSA enrichment
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 19:47 UTCGHSA enrichment
  22. 2026-08-15 06:56 UTCEG score recompute
  23. 2026-08-15 06:56 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 17:47 UTCGHSA enrichment
Show 47 more
  1. 2026-08-14 04:56 UTCEG score recompute
  2. 2026-08-14 04:56 UTCGHSA enrichment
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-13 16:05 UTCGHSA enrichment
  5. 2026-08-13 03:14 UTCGHSA enrichment
  6. 2026-08-12 14:23 UTCEG score recompute
  7. 2026-08-12 14:23 UTCGHSA enrichment
  8. 2026-08-12 13:50 UTCEPSS rescore
  9. 2026-08-12 01:31 UTCEG score recompute
  10. 2026-08-12 01:31 UTCGHSA enrichment
  11. 2026-08-11 13:42 UTCEPSS rescore
  12. 2026-08-11 12:40 UTCEG score recompute
  13. 2026-08-11 12:40 UTCGHSA enrichment
  14. 2026-08-11 00:00 UTCEPSS rescore
  15. 2026-08-10 23:46 UTCGHSA enrichment
  16. 2026-08-10 10:54 UTCGHSA enrichment
  17. 2026-08-09 22:03 UTCEG score recompute
  18. 2026-08-09 22:03 UTCGHSA enrichment
  19. 2026-08-09 13:46 UTCEPSS rescore
  20. 2026-08-09 09:12 UTCGHSA enrichment
  21. 2026-08-08 20:21 UTCEG score recompute
  22. 2026-08-08 20:21 UTCGHSA enrichment
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-08 07:29 UTCGHSA enrichment
  25. 2026-08-07 18:38 UTCEG score recompute
  26. 2026-08-07 18:38 UTCGHSA enrichment
  27. 2026-08-07 05:40 UTCGHSA enrichment
  28. 2026-08-06 16:49 UTCEG score recompute
  29. 2026-08-06 16:49 UTCGHSA enrichment
  30. 2026-08-06 13:46 UTCEPSS rescore
  31. 2026-08-06 03:57 UTCEG score recompute
  32. 2026-08-06 03:57 UTCGHSA enrichment
  33. 2026-08-05 19:17 UTCEPSS rescore
  34. 2026-08-05 15:06 UTCGHSA enrichment
  35. 2026-08-05 10:57 UTCGHSA enrichment
  36. 2026-08-04 22:05 UTCEG score recompute
  37. 2026-08-04 22:05 UTCGHSA enrichment
  38. 2026-08-04 15:10 UTCEPSS rescore
  39. 2026-08-04 09:13 UTCEG score recompute
  40. 2026-08-04 09:13 UTCGHSA enrichment
  41. 2026-08-03 20:19 UTCGHSA enrichment
  42. 2026-08-03 20:13 UTCEG score recompute 7.50
  43. 2026-08-03 20:13 UTCGHSA enrichment
  44. 2026-08-03 20:13 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  45. 2026-08-03 16:35 UTCNVD update
  46. 2026-08-03 15:28 UTCEG score recompute
  47. 2026-08-03 15:28 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-18568?
CVE-2026-18568 is a high vulnerability published on August 3, 2026. 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…
When was CVE-2026-18568 disclosed?
CVE-2026-18568 was first published in the National Vulnerability Database on August 3, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18568 actively exploited?
CVE-2026-18568 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.9% of all scored CVEs.
What is the CVSS score of CVE-2026-18568?
CVE-2026-18568 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-18568?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18568, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-18568

Explore →

Is Your Infrastructure Affected by CVE-2026-18568?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.