CVE-2026-50722

HIGHNVD 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 — Patch released this week
8.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0

A fix is available — apply it.

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 PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

July 2, 2026

Last Modified

July 9, 2026

Advisory Details (4)

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

RFC 8017: PKCS #1: RSA Cryptography Specifications Version 2.2 | RFC Editor

https://www.rfc-editor.org/rfc/rfc8017
generic
https://libreswan.org/security/CVE-2026-50722/CVE-2026-50722.txt
generic

Index of /security/CVE-2026-50722/

https://libreswan.org/security/CVE-2026-50722/
generic
https://libreswan.org/security/CVE-2026-50721/CVE-2026-50721.txt

Vendor Advisories for CVE-2026-50722(7)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatlibreswan-0:5.2-1.el10_0.52026-08-17redhat
redhatlibreswan-0:5.3.2-1.el9fdp2026-07-27redhat
redhatlibreswan-0:5.3.2-1.el10_22026-07-27redhat
redhatlibreswan-0:4.12-2.el8_10.62026-07-27redhat
redhatlibreswan-0:4.15-10.el9_82026-07-27redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libreswan4.10-1 ... 5.2-2.4 (27 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libreswan4.10-2 ... 5.2-2.4 (17 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libreswan5.2-2.2, 5.2-2.3, 5.2-2.4——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libreswan5.2-2.2, 5.2-2.3, 5.2-2.4——

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 40× in last 7d / 147× 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 216 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-50722?
CVE-2026-50722 is a high 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 0% probability of exploitation in the next 30 days, which ranks it in the top 72.2% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs