CVE-2026-50722

MEDIUMNVD 5.98.1
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-03. NVD baseline CVSS 5.9; sources differ by 2.2.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.9Exploit: NoneExposed: 0

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

Libreswan, via the function RSA_authenticate_hash_signature_pkcs1_1_5_rsa(), did not correctly verify the DER encoding of the ASN.1 digest when the IKEv2 AUTH payload was encoded using RSASSA-PKCS1-v1_5 (RFC 8017). A remote attacker can use a variation on the Bleichenbacher attack to forge the AUTH payload when small public exponents are used (e.g., e=3), leading to impersonation. Additionally, a remote attacker, by encoding a shorter than expected hash in the AUTH payload, could trigger an assertion leading to denial-of-service. The daemon aborts and restarts; continued exploitation causes sustained denial of service. Remote code execution is not possible. X.509 certificate verifications of the remote IKE peer are not affected.

CVSS v3
5.9
EG Score
8.1(medium)
EG Risk
52(Track)
EG Risk 52/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
Severity81% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
27.6%
KEV
Not listed

Published

July 2, 2026

Last Modified

July 9, 2026

Advisory Details (4)

Auto-updated Jul 3, 2026
No patch confirmed yet.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× 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-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:18 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-17 00:41 UTCVendor advisory
  11. 2026-07-17 00:40 UTCGHSA enrichment
  12. 2026-07-16 17:03 UTCEPSS rescore
  13. 2026-07-16 12:13 UTCVendor advisory
  14. 2026-07-16 12:13 UTCGHSA enrichment
  15. 2026-07-15 23:45 UTCVendor advisory
  16. 2026-07-15 23:45 UTCGHSA enrichment
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 16:57 UTCEPSS rescore
  19. 2026-07-15 11:18 UTCVendor advisory
  20. 2026-07-15 11:17 UTCGHSA enrichment
  21. 2026-07-15 02:00 UTCEPSS rescore
  22. 2026-07-15 02:00 UTCEPSS rescore
  23. 2026-07-14 22:51 UTCVendor advisory
  24. 2026-07-14 22:51 UTCGHSA enrichment
  25. 2026-07-14 10:24 UTCVendor advisory
Show 47 more
  1. 2026-07-14 10:24 UTCGHSA enrichment
  2. 2026-07-13 22:31 UTCEPSS rescore
  3. 2026-07-13 21:57 UTCGHSA enrichment
  4. 2026-07-13 09:30 UTCGHSA enrichment
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-12 21:02 UTCVendor advisory
  8. 2026-07-12 21:02 UTCGHSA enrichment
  9. 2026-07-12 08:31 UTCVendor advisory
  10. 2026-07-12 08:31 UTCGHSA enrichment
  11. 2026-07-12 05:46 UTCEPSS rescore
  12. 2026-07-11 20:04 UTCVendor advisory
  13. 2026-07-11 20:04 UTCGHSA enrichment
  14. 2026-07-11 08:27 UTCEPSS rescore
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-11 07:37 UTCVendor advisory
  17. 2026-07-11 07:36 UTCGHSA enrichment
  18. 2026-07-10 19:08 UTCVendor advisory
  19. 2026-07-10 19:08 UTCGHSA enrichment
  20. 2026-07-10 06:41 UTCGHSA enrichment
  21. 2026-07-09 19:10 UTCEPSS rescore
  22. 2026-07-09 19:10 UTCEPSS rescore
  23. 2026-07-09 18:13 UTCGHSA enrichment
  24. 2026-07-09 15:53 UTCNVD updateCVSS v3 → 5.9 · severity → MEDIUM
  25. 2026-07-09 05:46 UTCGHSA enrichment
  26. 2026-07-08 17:20 UTCGHSA enrichment
  27. 2026-07-08 15:16 UTCEPSS rescore
  28. 2026-07-08 15:16 UTCEPSS rescore
  29. 2026-07-08 04:51 UTCGHSA enrichment
  30. 2026-07-07 18:19 UTCNVD updateCVSS v3 → 8.1
  31. 2026-07-07 17:31 UTCMITRE cvelistV5CVSS v3 → 7.5
  32. 2026-07-07 16:14 UTCGHSA enrichment
  33. 2026-07-07 13:46 UTCEPSS rescore
  34. 2026-07-07 13:46 UTCEPSS rescore
  35. 2026-07-07 03:46 UTCGHSA enrichment
  36. 2026-07-06 16:27 UTCEPSS rescore
  37. 2026-07-06 15:18 UTCGHSA enrichment
  38. 2026-07-06 02:48 UTCGHSA enrichment
  39. 2026-07-06 02:23 UTCEPSS rescore
  40. 2026-07-05 14:22 UTCGHSA enrichment
  41. 2026-07-05 02:30 UTCEPSS rescore
  42. 2026-07-05 01:55 UTCGHSA enrichment
  43. 2026-07-04 13:28 UTCGHSA enrichment
  44. 2026-07-04 01:01 UTCGHSA enrichment
  45. 2026-07-03 12:35 UTCGHSA enrichment
  46. 2026-07-03 00:06 UTCEG score recompute
  47. 2026-07-03 00:06 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-50722?
CVE-2026-50722 is a medium vulnerability published on July 2, 2026. Libreswan, via the function RSAauthenticatehashsignaturepkcs115rsa(), did not correctly verify the DER encoding of the ASN.1 digest when the IKEv2 AUTH payload was encoded using RSASSA-PKCS1-v15 (RFC 8017). A remote attacker can use a variation on the Bleichenbacher attack to forge the AUTH payload…
When was CVE-2026-50722 disclosed?
CVE-2026-50722 was first published in the National Vulnerability Database on July 2, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50722 actively exploited?
CVE-2026-50722 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-50722?
CVE-2026-50722 has a CVSS v3 base score of 5.9 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.1.
How do I remediate CVE-2026-50722?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50722, 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-50722

Explore →

Is Your Infrastructure Affected by CVE-2026-50722?

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