IKE daemon crash via missing issuerName check
Published Sep 11, 2026 · Updated Sep 11, 2026
NULL pointer dereference in strongSwan 4.2.0 through 6.0.7 allows attackers to crash the IKE daemon via a crafted attribute certificate. During verification, issued_by() calls issuerName->equals() without checking whether the optional issuerName field was parsed; has_issuer() similarly calls matches(). Exposure requires both the x509 and acert plugins to be loaded, and successful exploitation interrupts the VPN service without enabling code execution.
Summary
What happened
NULL pointer dereference in strongSwan 4.2.0 through 6.0.7 allows attackers to crash the IKE daemon via a crafted attribute certificate. During verification, issued_by() calls issuerName->equals() without checking whether the optional issuerName field was parsed; has_issuer() similarly calls matches(). Exposure requires both the x509 and acert plugins to be loaded, and successful exploitation interrupts the VPN service without enabling code execution.
The record
- CVE
- CVE-2026-78130
- Published
- Sep 11, 2026
- Updated
- Sep 11, 2026
- Vendor
- strongSwan
- Product
- strongSwan
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 11, 2026CVE publishedPublication date reported by the CVE source.
- Sep 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.2.0 <6.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo