CVE-2026-47895

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-23. 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: 0.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In strongSwan before 6.0.7, identity parsing/cloning is mishandled. Parsed EAP-Identities that result in an empty but non-NULL encoding are not correctly cloned and trigger a double-free once the duplicates are destroyed.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100CISA SSVC

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%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 22, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Aug 22, 2026
Patch available. Sources: github_release.
generic

strongSwan - Download

https://www.strongswan.org/download.html
github_release Patch Available

strongSwan 6.0.7

Patch available: strongswan/strongswan 6.0.7

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

Vendor Advisories for CVE-2026-47895(2)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntustrongswan-swanctl (6.0.4-1ubuntu3.1) @ resolute2026-10-07ubuntu

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.24(1)
PackageVulnerable rangeFix by version rangeDependents
strongswan—
  • every version up to 6.0.7-r0: fixed in 6.0.7-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
strongswan5.9.8-5, 5.9.8-5+deb12u1, 5.9.8-5+deb12u2, 5.9.8-5+deb12u3, 5.9.8-5+deb12u4
  • every version up to 5.9.8-5+deb12u5: fixed in 5.9.8-5+deb12u5
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
strongswan6.0.1-6, 6.0.1-6+deb13u1, 6.0.1-6+deb13u2, 6.0.1-6+deb13u4, 6.0.1-6+deb13u5
  • every version up to 6.0.1-6+deb13u6: fixed in 6.0.1-6+deb13u6
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
strongswan6.0.1-6 ... 6.0.6-1 (6 versions)
  • every version up to 6.0.7-1: fixed in 6.0.7-1
—

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 28× in last 7d / 155× 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 269 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-47895?
CVE-2026-47895 is a high vulnerability published on August 22, 2026. In strongSwan before 6.0.7, identity parsing/cloning is mishandled. Parsed EAP-Identities that result in an empty but non-NULL encoding are not correctly cloned and trigger a double-free once the duplicates are destroyed.
When was CVE-2026-47895 disclosed?
CVE-2026-47895 was first published on August 22, 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-47895 actively exploited?
CVE-2026-47895 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47895?
CVE-2026-47895 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-47895?
A fix for CVE-2026-47895 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47895 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-47895

Explore →

Is Your Infrastructure Affected by CVE-2026-47895?

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

Book a Demo →Browse All CVEs