CVE-2026-18108

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

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

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

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

Net::SAML2 versions before 0.86 for Perl allow authentication bypass because _verify_encrypted_assertion accepts an EncryptedAssertion whose decrypted content carries no signature.

_verify_encrypted_assertion decrypts the EncryptedAssertion and returns it as verified when it carries no signature, via "return $xml unless $xpath->exists('dsig:Signature', $assert);". The signature check and the trust anchor check that follow run only when a signature is present, so a decrypted assertion with no dsig:Signature element reaches new_from_xml unverified and its NameID and attributes are read into the assertion object. An SP's encryption certificate is published in its SAML metadata so the IdP can encrypt to it, so any party can encrypt an unsigned assertion to that certificate, wrap it in a samlp:Response, and post it to the assertion consumer service.

Any caller that configures a decryption key_file, and so accepts EncryptedAssertions, takes identity fields from an assertion that no trust anchor covers, and an unauthenticated party can authenticate as an arbitrary user. Callers with no key_file configured do not decrypt and are unaffected.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
59(Track)
EG Risk 59/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
Severity98% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

August 3, 2026

Last Modified

August 6, 2026

Vendor Advisories for CVE-2026-18108(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 53× in last 7d / 140× 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.

Showing the most recent 100 of 140 total refreshes for this CVE.

  1. 2026-08-21 07:24 UTCGHSA enrichment
  2. 2026-08-21 03:08 UTCEG score recompute
  3. 2026-08-21 03:08 UTCGHSA enrichment
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 22:52 UTCGHSA enrichment
  6. 2026-08-20 18:37 UTCGHSA enrichment
  7. 2026-08-20 14:21 UTCGHSA enrichment
  8. 2026-08-20 09:25 UTCGHSA enrichment
  9. 2026-08-20 05:10 UTCGHSA enrichment
  10. 2026-08-20 00:54 UTCGHSA enrichment
  11. 2026-08-19 20:35 UTCEG score recompute
  12. 2026-08-19 20:35 UTCGHSA enrichment
  13. 2026-08-19 17:03 UTCEPSS rescore
  14. 2026-08-19 16:19 UTCGHSA enrichment
  15. 2026-08-19 11:52 UTCGHSA enrichment
  16. 2026-08-19 07:36 UTCGHSA enrichment
  17. 2026-08-19 03:21 UTCGHSA enrichment
  18. 2026-08-18 22:37 UTCGHSA enrichment
  19. 2026-08-18 18:20 UTCEG score recompute
  20. 2026-08-18 18:20 UTCGHSA enrichment
  21. 2026-08-18 13:48 UTCEPSS rescore
  22. 2026-08-18 13:02 UTCGHSA enrichment
  23. 2026-08-18 08:40 UTCGHSA enrichment
  24. 2026-08-18 04:12 UTCGHSA enrichment
  25. 2026-08-17 23:53 UTCGHSA enrichment
Show 75 more
  1. 2026-08-17 19:37 UTCGHSA enrichment
  2. 2026-08-17 15:05 UTCEG score recompute
  3. 2026-08-17 15:05 UTCGHSA enrichment
  4. 2026-08-17 13:47 UTCEPSS rescore
  5. 2026-08-17 10:49 UTCGHSA enrichment
  6. 2026-08-17 06:34 UTCGHSA enrichment
  7. 2026-08-17 02:12 UTCGHSA enrichment
  8. 2026-08-16 21:56 UTCGHSA enrichment
  9. 2026-08-16 17:40 UTCEG score recompute
  10. 2026-08-16 17:40 UTCGHSA enrichment
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 13:20 UTCGHSA enrichment
  13. 2026-08-16 09:04 UTCGHSA enrichment
  14. 2026-08-16 04:48 UTCEG score recompute
  15. 2026-08-16 04:48 UTCGHSA enrichment
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-16 00:33 UTCGHSA enrichment
  18. 2026-08-15 20:17 UTCGHSA enrichment
  19. 2026-08-15 16:01 UTCGHSA enrichment
  20. 2026-08-15 11:45 UTCGHSA enrichment
  21. 2026-08-15 07:29 UTCGHSA enrichment
  22. 2026-08-15 03:13 UTCEG score recompute
  23. 2026-08-15 03:13 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 22:57 UTCGHSA enrichment
  26. 2026-08-14 18:42 UTCGHSA enrichment
  27. 2026-08-14 14:26 UTCGHSA enrichment
  28. 2026-08-14 10:11 UTCGHSA enrichment
  29. 2026-08-14 05:55 UTCGHSA enrichment
  30. 2026-08-14 01:40 UTCEG score recompute
  31. 2026-08-14 01:40 UTCGHSA enrichment
  32. 2026-08-13 22:00 UTCEPSS rescore
  33. 2026-08-13 21:24 UTCGHSA enrichment
  34. 2026-08-13 17:08 UTCGHSA enrichment
  35. 2026-08-13 12:52 UTCGHSA enrichment
  36. 2026-08-13 08:37 UTCGHSA enrichment
  37. 2026-08-13 04:21 UTCGHSA enrichment
  38. 2026-08-13 00:05 UTCGHSA enrichment
  39. 2026-08-12 19:50 UTCGHSA enrichment
  40. 2026-08-12 15:34 UTCEG score recompute
  41. 2026-08-12 15:34 UTCGHSA enrichment
  42. 2026-08-12 13:50 UTCEPSS rescore
  43. 2026-08-12 11:19 UTCGHSA enrichment
  44. 2026-08-12 07:03 UTCGHSA enrichment
  45. 2026-08-12 02:47 UTCGHSA enrichment
  46. 2026-08-11 22:32 UTCGHSA enrichment
  47. 2026-08-11 18:17 UTCGHSA enrichment
  48. 2026-08-11 13:55 UTCEG score recompute
  49. 2026-08-11 13:55 UTCGHSA enrichment
  50. 2026-08-11 13:42 UTCEPSS rescore
  51. 2026-08-11 09:39 UTCGHSA enrichment
  52. 2026-08-11 05:24 UTCGHSA enrichment
  53. 2026-08-11 01:08 UTCEG score recompute
  54. 2026-08-11 01:08 UTCGHSA enrichment
  55. 2026-08-11 00:00 UTCEPSS rescore
  56. 2026-08-10 20:53 UTCGHSA enrichment
  57. 2026-08-10 16:37 UTCGHSA enrichment
  58. 2026-08-10 12:11 UTCGHSA enrichment
  59. 2026-08-10 07:55 UTCGHSA enrichment
  60. 2026-08-10 03:40 UTCGHSA enrichment
  61. 2026-08-09 23:24 UTCGHSA enrichment
  62. 2026-08-09 19:09 UTCGHSA enrichment
  63. 2026-08-09 14:53 UTCEG score recompute
  64. 2026-08-09 14:53 UTCGHSA enrichment
  65. 2026-08-09 13:46 UTCEPSS rescore
  66. 2026-08-09 10:38 UTCGHSA enrichment
  67. 2026-08-09 06:22 UTCGHSA enrichment
  68. 2026-08-09 02:06 UTCGHSA enrichment
  69. 2026-08-08 21:51 UTCGHSA enrichment
  70. 2026-08-08 17:35 UTCEG score recompute
  71. 2026-08-08 17:35 UTCGHSA enrichment
  72. 2026-08-08 16:37 UTCEPSS rescore
  73. 2026-08-08 13:19 UTCGHSA enrichment
  74. 2026-08-08 09:03 UTCGHSA enrichment
  75. 2026-08-08 04:48 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-18108?
CVE-2026-18108 is a critical vulnerability published on August 3, 2026. Net::SAML2 versions before 0.86 for Perl allow authentication bypass because verifyencrypted_assertion accepts an EncryptedAssertion whose decrypted content carries no signature. verifyencryptedassertion decrypts the EncryptedAssertion and returns it as verified when it carries no signature, via…
When was CVE-2026-18108 disclosed?
CVE-2026-18108 was first published in the National Vulnerability Database on August 3, 2026, with the most recent update on August 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18108 actively exploited?
CVE-2026-18108 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 87.2% of all scored CVEs.
What is the CVSS score of CVE-2026-18108?
CVE-2026-18108 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-18108?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18108, 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-18108

Explore →

Is Your Infrastructure Affected by CVE-2026-18108?

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