CVE-2026-78133 json
libcharon in strongSwan 6.0.0 through 6.0.7 has a use-after-free in IKEv2 rekeying collision handling.
published 2026-09-11 59 d ago modified 2026-09-14 55 d ago also EUVD-2026-75907
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
Summary
libcharon in strongSwan 6.0.0 through 6.0.7 has a use-after-free in IKEv2 rekeying collision handling.
Patch / fix
- strongSwan strongSwan 6.1.0
- strongswan Debian 13 6.0.1-6+deb13u7
- strongswan Debian 14 6.1.0-1
debian advisories DEBIAN-CVE-2026-78133
- strongswan Ubuntu 26.04 LTS 6.0.4-1ubuntu3.2
ubuntu advisories UBUNTU-CVE-2026-78133
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- strongswan SLES for SAP applications 16.0, SLES 16.0 6.0.6-160000.3.1
suse advisories SUSE-SU-2026:24199-1
- strongswan openSUSE Leap 16.0 6.0.6-160000.3.1
- strongswan openSUSE Tumbleweed 6.1.0-1.1
opensuse advisories openSUSE-SU-2026:22050-1openSUSE-SU-2026:11749-1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 58 d ago
Exploit prediction
0.47% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- strongSwan strongSwan
Classification
- Weakness
-
- CWE-416 Use After Free
References
-
github.com
/strongswan/strongswan/releases/tag/6.1.0
patch, release-notes, vendor-advisory
-
strongswan.org
/blog/2026/09/07/strongswan-vulnerability-(cve-2026-78133).html
mitigation, vendor-advisory
Sources
- CVE List CVE-2026-78133
- NVD CVE-2026-78133
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.