# CVE-2026-25075: strongSwan 4.5.0 < 6.0.5 EAP-TTLS AVP Parsing Integer Underflow > Unauthenticated remote attackers can crash the strongSwan IKE daemon via crafted EAP-TTLS AVP data, causing denial of service. - **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 23 Mar 2026 - **Updated:** 14 Jul 2026 - **Also known as:** AZL-80300, DEBIAN-CVE-2026-25075, DLA-4512-1, DSA-6176-1, GHSA-frr2-5qjr-h4hw, MGASA-2026-0072, SUSE-SU-2026:0978-1, SUSE-SU-2026:0979-1, SUSE-SU-2026:0980-1, SUSE-SU-2026:0981-1, SUSE-SU-2026:1307-1, UBUNTU-CVE-2026-25075, USN-8117-1, openSUSE-SU-2026:10441-1 ## What is CVE-2026-25075? CVE-2026-25075 is a high-severity vulnerability in strongSwan, published on 23 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description strongSwan versions 4.5.0 prior to 6.0.5 contain an integer underflow vulnerability in the EAP-TTLS AVP parser that allows unauthenticated remote attackers to cause a denial of service by sending crafted AVP data with invalid length fields during IKEv2 authentication. Attackers can exploit the failure to validate AVP length fields before subtraction to trigger excessive memory allocation or NULL pointer dereference, crashing the charon IKE daemon. Weakness: CWE-476 (NULL Pointer Dereference), CWE-191 (Integer Underflow (Wrap or Wraparound)) ## Which versions are affected by CVE-2026-25075? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `strongswan` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 5.9.11-150400.19.26.1 | | `strongswan` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 5.9.11-150400.19.26.1 | | `strongswan` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 5.9.11-150500.5.14.1 | | `strongswan` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 5.9.11-150500.5.14.1 | | `strongswan` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 5.9.14-150700.3.9.1 | | `strongswan` | SUSE:Linux Enterprise Module for Package Hub 15 SP7 | All versions | 5.9.14-150700.3.9.1 | | `strongswan` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 5.1.3-26.32.1 | | `strongswan` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 5.9.11-150400.19.26.1 | | `strongswan` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 5.9.11-150500.5.14.1 | | `strongswan` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 5.9.12-150600.3.11.1 | | `strongswan` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 5.1.3-26.32.1 | | `strongswan` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 5.9.11-150400.19.26.1 | | `strongswan` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 5.9.11-150500.5.14.1 | | `strongswan` | SUSE:Linux Enterprise Server for SAP Applications 15 SP6 | All versions | 5.9.12-150600.3.11.1 | | `strongswan` | SUSE:Linux Enterprise Workstation Extension 15 SP7 | All versions | 5.9.14-150700.3.9.1 | | `strongswan` | openSUSE:Leap 15.6 | All versions | 5.9.12-150600.3.11.1 | | `strongswan` | openSUSE:Tumbleweed | All versions | 6.0.5-1.1 | ## How do I fix CVE-2026-25075? Upgrade to a fixed version. ## Is CVE-2026-25075 being exploited? There is no known exploitation of CVE-2026-25075 in the wild and no public exploit code. Public exploit code: - https://github.com/BishopFox/CVE-2026-25075-check (github_poc): https://github.com/BishopFox/CVE-2026-25075-check ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-25075 and fix it if it is affected. What it is: CVE-2026-25075 is a high-severity vulnerability in strongSwan, published on 23 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-25075 in the wild and no public exploit code. Affected product: strongSwan. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-25075/ (Markdown: https://insights.sbomify.com/CVE-2026-25075/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25075 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25075 - OSV: https://osv.dev/vulnerability/CVE-2026-25075 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-25075/ Summaries are generated and may contain mistakes; the official description above is the record.