CVE-2026-78129

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreHIGH confidence

Score 5.9 from GitHub Security Advisory published 2026-09-11. a secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
5.9EG
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

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

strongSwan 4.6.2 through 6.0.7 has an infinite loop in PKCS#5 decryption.

CVSS v3
5.9
EG Score
5.9(high)
EG Risk
27(Track)
EG Risk 27/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
Severity59% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

September 11, 2026

Last Modified

September 14, 2026

Advisory Details (2)

Auto-updated Sep 11, 2026
Patch available. Sources: github_release.
generic

strongSwan - strongSwan Vulnerability (CVE-2026-78129)

https://www.strongswan.org/blog/2026/09/07/strongswan-vulnerability-(cve-2026-78129).html
github_release Patch Available

strongSwan 6.1.0

Patch available: strongswan/strongswan 6.1.0

https://github.com/strongswan/strongswan/releases/tag/6.1.0

Vendor Advisories for CVE-2026-78129(1)

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

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 27× in last 7d / 38× 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-09-19 17:47 UTCEG score recompute
  2. 2026-09-19 17:47 UTCVendor advisory
  3. 2026-09-19 17:47 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 18:46 UTCVendor advisory
  6. 2026-09-18 18:46 UTCGHSA enrichment
  7. 2026-09-17 19:45 UTCEG score recompute
  8. 2026-09-17 19:45 UTCVendor advisory
  9. 2026-09-17 19:45 UTCGHSA enrichment
  10. 2026-09-16 18:16 UTCEG score recompute
  11. 2026-09-16 18:16 UTCVendor advisory
  12. 2026-09-16 18:16 UTCGHSA enrichment
  13. 2026-09-16 14:08 UTCEPSS rescore
  14. 2026-09-16 05:15 UTCEPSS rescore
  15. 2026-09-15 19:15 UTCEG score recompute
  16. 2026-09-15 19:15 UTCVendor advisory
  17. 2026-09-15 19:15 UTCGHSA enrichment
  18. 2026-09-15 03:12 UTCEPSS rescore
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-14 20:14 UTCVendor advisory
  21. 2026-09-14 20:14 UTCGHSA enrichment
  22. 2026-09-14 12:37 UTCEG score recompute
  23. 2026-09-14 12:37 UTCVendor advisory
  24. 2026-09-14 12:37 UTCGHSA enrichment
  25. 2026-09-13 13:31 UTCEG score recompute
Show 13 more
  1. 2026-09-13 13:31 UTCVendor advisory
  2. 2026-09-13 13:31 UTCGHSA enrichment
  3. 2026-09-12 14:30 UTCGHSA enrichment
  4. 2026-09-11 15:29 UTCGHSA enrichment
  5. 2026-09-11 15:07 UTCEG score recompute
  6. 2026-09-11 15:07 UTCGHSA enrichment
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 14:20 UTCEG score recompute
  10. 2026-09-11 14:20 UTCGHSA enrichment
  11. 2026-09-11 02:20 UTCEG score recompute
  12. 2026-09-11 01:45 UTCEG score recompute
  13. 2026-09-11 01:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-78129?
CVE-2026-78129 is a medium vulnerability published on September 11, 2026. strongSwan 4.6.2 through 6.0.7 has an infinite loop in PKCS#5 decryption.
When was CVE-2026-78129 disclosed?
CVE-2026-78129 was first published in the National Vulnerability Database on September 11, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-78129 actively exploited?
CVE-2026-78129 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 64.8% of all scored CVEs.
What is the CVSS score of CVE-2026-78129?
CVE-2026-78129 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-78129?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-78129, 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-78129

Explore →

Is Your Infrastructure Affected by CVE-2026-78129?

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