Unauthenticated daemon crash via malformed AVP length
Published Mar 23, 2026 · Updated Mar 23, 2026
Integer underflow in strongSwan 4.5.0 through 6.0.4 allows remote attackers to crash the charon daemon via crafted EAP-TTLS AVPs. The EAP-TTLS AVP process method subtracts the eight-byte header size without first rejecting lengths below eight, producing a huge allocation length and a NULL dereference. The eap-ttls plugin must be enabled and reachable during IKEv2 authentication; no credentials or user interaction are required, and the consequence is a VPN service interruption.
Summary
What happened
Integer underflow in strongSwan 4.5.0 through 6.0.4 allows remote attackers to crash the charon daemon via crafted EAP-TTLS AVPs. The EAP-TTLS AVP process method subtracts the eight-byte header size without first rejecting lengths below eight, producing a huge allocation length and a NULL dereference. The eap-ttls plugin must be enabled and reachable during IKEv2 authentication; no credentials or user interaction are required, and the consequence is a VPN service interruption.
The record
- CVE
- CVE-2026-25075
- Published
- Mar 23, 2026
- Updated
- Mar 23, 2026
- Vendor
- strongSwan
- Product
- strongSwan
- Classifications
- CWE-191, CWE-476, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 23, 2026CVE publishedPublication date reported by the CVE source.
- Mar 23, 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.5.0 <6.0.5
What conditions does exploitation require?
What is affected?
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