CVE-2026-14957

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-69820 (ENISA EUVD) · GHSA-x2hf-3rgr-r89x (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (Libreswan Project) states them: "Upgrade to libreswan 5.3.2 or later."

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.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 2, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Sep 2, 2026
Patch available.

Patch Availability(14)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatlibreswan-0:4.3-6.el8_4.22026-10-19redhat
redhatlibreswan-0:4.5-1.el8_6.62026-10-13redhat
redhatlibreswan-0:4.9-3.el8_8.32026-09-28redhat
redhatopenshift/ose-rhel-coreos-9:4.19.9.6.202609021231-02026-09-09redhat
redhatopenshift/ose-rhel-coreos-9:4.20.9.6.202609021029-02026-09-08redhat
redhatopenshift/ose-rhel-coreos-9:4.21.9.6.202609021100-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 rangeFix by version rangeDependents
libreswan4.10-2 ... 5.2-2.5 (18 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libreswan5.2-2.2, 5.2-2.3, 5.2-2.4, 5.2-2.5
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libreswan5.2-2.2, 5.2-2.3, 5.2-2.4
  • every version up to 5.2-2.5: fixed in 5.2-2.5
—

Weakness Classification(2)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 74× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 253 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 153 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-14957?
CVE-2026-14957 is a high-severity vulnerability; its CVE record was published on September 2, 2026. 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…
When was the CVE record for CVE-2026-14957 published?
The CVE record for CVE-2026-14957 was published on September 2, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-14957 actively exploited?
CVE-2026-14957 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-14957?
CVE-2026-14957 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-14957?
A fix for CVE-2026-14957 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (Libreswan Project) states them: "Upgrade to libreswan 5.3.2 or later." The vendor advisories EchelonGraph has for CVE-2026-14957 are linked in the Vendor Advisories panel on this page.

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.