CVE-2026-14957

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-02. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 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: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

In FIPS mode, Libreswan's add_decoded_cert() function calls CERT_ExtractPublicKey() and asserts that the result is not NULL. However, CERT_ExtractPublicKey() returns NULL when public key extraction fails, for example if the RSA exponent is set to 0. A remote attacker can send a malformed X.509 certificate in a CERT payload to trigger the assertion, causing the pluto daemon to abort and restart. Continued exploitation causes a denial of service. No remote code execution is possible. Both IKEv1 and IKEv2 are affected. The vulnerability is only exploitable when both the OS and libreswan are running in FIPS mode and at least one CA certificate is loaded. The CERT payload is processed before peer authentication, so no credentials are needed to exploit this. Configurations using only PreSharedKey (PSK) authentication with no CA certificates loaded in the NSS database are not vulnerable.

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%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

September 2, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Sep 2, 2026
No patch confirmed yet.
generic

Index of /security/CVE-2026-14957/

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

Vendor Advisories for CVE-2026-14957(13)

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

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhcos-4.19.9.6.202609021231-02026-09-09redhat
redhatrhcos-4.21.9.6.202609021100-02026-09-08redhat
redhatrhcos-4.20.9.6.202609021029-02026-09-08redhat
redhatlibreswan-0:4.12-3.el9_4.22026-08-31redhat
redhatlibreswan-0:4.9-5.el9_2.52026-08-31redhat
redhatlibreswan-0:4.15-8.el9_6.12026-08-20redhat
redhatlibreswan-0:5.2-1.el10_0.52026-08-17redhat
redhatlibreswan-0:4.15-10.el9_82026-07-27redhat
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

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libreswan4.10-2 ... 5.2-2.5 (18 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libreswan5.2-2.2, 5.2-2.3, 5.2-2.4, 5.2-2.5——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libreswan5.2-2.2, 5.2-2.3, 5.2-2.45.2-2.5—

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-14957?
CVE-2026-14957 is a high vulnerability published on September 2, 2026. In FIPS mode, Libreswan's adddecodedcert() function calls CERTExtractPublicKey() and asserts that the result is not NULL. However, CERTExtractPublicKey() returns NULL when public key extraction fails, for example if the RSA exponent is set to 0. A remote attacker can send a malformed X.509…
When was CVE-2026-14957 disclosed?
CVE-2026-14957 was first published in the National Vulnerability Database on September 2, 2026, with the most recent update on September 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-14957 actively exploited?
CVE-2026-14957 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.9% of all scored CVEs.
What is the CVSS score of CVE-2026-14957?
CVE-2026-14957 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-14957?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14957, 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-14957

Explore →

Is Your Infrastructure Affected by CVE-2026-14957?

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

Start Free Scan →Browse All CVEs