CVE-2026-25075

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-03-23. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

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%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
62%
KEV
Not listed

Published

March 23, 2026

Last Modified

July 14, 2026

Advisory Details (4)

Auto-updated May 1, 2026
Patch available.
generic Patch Available

[SECURITY] [DLA 4512-1] strongswan security update

https://lists.debian.org/debian-lts-announce/2026/03/msg00016.html
generic

strongSwan 4.5.0 < 6.0.5 EAP-TTLS AVP Parsing Integer Underflow | Advisories | VulnCheck

https://www.vulncheck.com/advisories/strongswan-eap-ttls-avp-parsing-integer-underflow
generic

strongSwan - strongSwan Vulnerability (CVE-2026-25075)

https://www.strongswan.org/blog/2026/03/23/strongswan-vulnerability-(cve-2026-25075).html
generic

strongSwan - strongSwan 6.0.5 Released

https://www.strongswan.org/blog/2026/03/23/strongswan-6.0.5-released.html

Vendor Advisories for CVE-2026-25075(1)

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 / EcosystemFixed in / PatchReleasedSource
ubuntustrongswan-swanctl (6.0.1-6ubuntu4.2) @ questing2026-06-11ubuntu

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)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
strongswan5.9.1-1 ... 5.9.1-1+deb11u5 (6 versions)5.9.1-1+deb11u6—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
strongswan5.9.8-5, 5.9.8-5+deb12u1, 5.9.8-5+deb12u25.9.8-5+deb12u3—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
strongswan6.0.1-6, 6.0.1-6+deb13u1, 6.0.1-6+deb13u26.0.1-6+deb13u4—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
strongswan6.0.1-6, 6.0.2-1, 6.0.3-1, 6.0.4-16.0.5-1—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 4× in last 7d / 25× 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 227 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCBishopFox/CVE-2026-25075-check
    First seen Mar 26, 2026
    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-25075?
CVE-2026-25075 is a high vulnerability published on March 23, 2026. 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…
When was CVE-2026-25075 disclosed?
CVE-2026-25075 was first published in the National Vulnerability Database on March 23, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-25075 actively exploited?
CVE-2026-25075 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 38.3% of all scored CVEs.
What is the CVSS score of CVE-2026-25075?
CVE-2026-25075 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-25075?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25075, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-25075

Explore →

Is Your Infrastructure Affected by CVE-2026-25075?

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

Start Free Scan →Browse All CVEs