CVE-2026-77207

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-10-14. 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 — Patch released this week

Also known asEUVD-2026-100749 (ENISA EUVD) · GHSA-jf6r-wr9w-j67c (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.3 or 5.4.1 or later."

Libreswan has a null pointer dereference bug in the PKCS#7 handling code for IKE certificate authentication. When libreswan decodes an IKE CERT payload of type CERT_PKCS7_WRAPPED_X509, it guards the PKCS#7 blob with SEC_PKCS7ContainsCertsOrCrls() and then iterates the certificate list with SEC_PKCS7GetCertificateList(). The two NSS APIs disagree on a SignedData that carries a CRL but no certificates: ContainsCertsOrCrls() returns PR_TRUE (there is a CRL), so the guard passes, but GetCertificateList() returns NULL (there are no certificates). This causes libreswan to dereference a null pointer leading to a crash and restart. A malicious IKE_AUTH packet can trigger this bug, meaning the peer does not need to be authenticated. No remote code execution is possible. Continued exploitation can cause a denial of service.

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-11-12). 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

October 13, 2026

Last Modified

October 16, 2026

Advisory Details (2)

Auto-updated Oct 13, 2026
Patch available.

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatlibreswan-0:5.3.3-3.el9fdp2026-11-11redhat
redhatlibreswan-0:5.4.1-1.el10_32026-11-11redhat
redhatlibreswan-0:4.15-11.el9_92026-11-10redhat
redhatopenshift/ose-rhel-coreos-9:5.0.10.2.202611022203-02026-11-09redhat
redhatopenshift/ose-rhel-coreos-9:4.22.9.8.202611032353-02026-11-06redhat
redhatlibreswan-0:4.15-11.el9_82026-10-26redhat
redhatlibreswan-0:5.3.3-1.el10_22026-10-26redhat
redhatlibreswan-0:4.12-2.el8_10.72026-10-26redhat

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)
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
libreswan—
  • every version up to 5.3.3-r0: fixed in 5.3.3-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
libreswan—
  • every version up to 5.3.3-r0: fixed in 5.3.3-r0
—
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
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 39× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 00:33 UTCEchelonGraph re-scored
  2. 2026-11-13 00:33 UTCVendor advisory
  3. 2026-11-13 00:33 UTCGHSA enrichmentGHSA-jf6r-wr9w-j67c · GitHub severity HIGH · GitHub CVSS 7.5
  4. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  6. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  7. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-11-07 18:00 UTCEchelonGraph re-scored
  10. 2026-11-07 18:00 UTCVendor advisory
  11. 2026-11-07 18:00 UTCGHSA enrichmentGHSA-jf6r-wr9w-j67c · GitHub severity HIGH · GitHub CVSS 7.5
  12. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  15. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  16. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  18. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  19. 2026-10-31 10:44 UTCEchelonGraph re-scored
  20. 2026-10-31 10:44 UTCVendor advisory
  21. 2026-10-31 10:44 UTCGHSA enrichmentGHSA-jf6r-wr9w-j67c · GitHub severity HIGH · GitHub CVSS 7.5
  22. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
Show 25 more
  1. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  3. 2026-10-25 14:01 UTCEchelonGraph re-scored
  4. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  5. 2026-10-24 03:27 UTCEchelonGraph re-scored
  6. 2026-10-24 03:27 UTCGHSA enrichmentGHSA-jf6r-wr9w-j67c · GitHub severity HIGH · GitHub CVSS 7.5
  7. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  8. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  9. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  10. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  11. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  12. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  13. 2026-10-18 03:12 UTCEchelonGraph re-scored
  14. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  15. 2026-10-16 20:11 UTCGHSA enrichmentGHSA-jf6r-wr9w-j67c · GitHub severity HIGH · GitHub CVSS 7.5
  16. 2026-10-16 17:12 UTCEchelonGraph re-scored
  17. 2026-10-16 17:11 UTCGHSA enrichmentGHSA-jf6r-wr9w-j67c · GitHub severity HIGH · GitHub CVSS 7.5
  18. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  19. 2026-10-16 15:47 UTCEchelonGraph re-scored
  20. 2026-10-16 15:46 UTCGHSA enrichmentGHSA-jf6r-wr9w-j67c · GitHub severity HIGH · GitHub CVSS 7.5
  21. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  22. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  23. 2026-10-13 22:27 UTCEchelonGraph re-scored
  24. 2026-10-13 21:34 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  25. 2026-10-13 21:34 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-77207?
CVE-2026-77207 is a high-severity vulnerability; its CVE record was published on October 13, 2026. Libreswan has a null pointer dereference bug in the PKCS#7 handling code for IKE certificate authentication. When libreswan decodes an IKE CERT payload of type CERT_PKCS7_WRAPPED_X509, it guards the PKCS#7 blob with SEC_PKCS7ContainsCertsOrCrls() and then iterates the certificate list with…
When was the CVE record for CVE-2026-77207 published?
The CVE record for CVE-2026-77207 was published on October 13, 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 October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-77207 actively exploited?
CVE-2026-77207 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-77207?
CVE-2026-77207 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-77207?
A fix for CVE-2026-77207 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.3 or 5.4.1 or later." The vendor advisories EchelonGraph has for CVE-2026-77207 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-77207

Explore →

Is Your Infrastructure Affected by CVE-2026-77207?

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