CVE-2026-25075

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-14477 (ENISA EUVD) · GHSA-frr2-5qjr-h4hw (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.1%
EPSS %ILE
65th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.1% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 23, 2026

Last Modified

July 14, 2026

Advisory Details (4)

Auto-updated May 1, 2026
Patch available.
Web pageMentions a patch (unverified)

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

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

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
Web page

strongSwan - strongSwan Vulnerability (CVE-2026-25075)

https://www.strongswan.org/blog/2026/03/23/strongswan-vulnerability-(cve-2026-25075).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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntustrongswan-swanctl (6.0.1-6ubuntu4.2) @ questing2026-11-03ubuntu

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 rangeFix by version rangeDependents
strongswan5.9.1-1 ... 5.9.1-1+deb11u5 (6 versions)
  • every version up to 5.9.1-1+deb11u6: fixed in 5.9.1-1+deb11u6
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
strongswan5.9.8-5, 5.9.8-5+deb12u1, 5.9.8-5+deb12u2
  • every version up to 5.9.8-5+deb12u3: fixed in 5.9.8-5+deb12u3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
strongswan6.0.1-6, 6.0.1-6+deb13u1, 6.0.1-6+deb13u2
  • every version up to 6.0.1-6+deb13u4: fixed in 6.0.1-6+deb13u4
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
strongswan6.0.1-6, 6.0.2-1, 6.0.3-1, 6.0.4-1
  • every version up to 6.0.5-1: fixed in 6.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 8× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 300 rows on record for this CVE, as 99 entries (1 repeat merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 200 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:33 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  2. 2026-11-11 16:39 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  3. 2026-11-10 16:43 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  4. 2026-11-09 16:34 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  5. 2026-11-09 14:17 UTCEchelonGraph re-scored
  6. 2026-11-09 14:17 UTCGHSA enrichmentGHSA-frr2-5qjr-h4hw · GitHub severity HIGH · GitHub CVSS 7.5
  7. 2026-11-08 16:38 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  8. 2026-11-07 16:38 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  9. 2026-11-06 16:37 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  10. 2026-11-05 16:37 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  11. 2026-11-04 16:35 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  12. 2026-11-03 16:47 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  13. 2026-11-03 00:40 UTCEchelonGraph re-scored
  14. 2026-11-03 00:40 UTCVendor advisory
  15. 2026-11-03 00:40 UTCGHSA enrichmentGHSA-frr2-5qjr-h4hw · GitHub severity HIGH · GitHub CVSS 7.5
  16. 2026-11-02 16:44 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  17. 2026-10-31 16:32 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  18. 2026-10-30 16:34 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  19. 2026-10-29 16:32 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  20. 2026-10-28 16:31 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  21. 2026-10-27 16:31 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  22. 2026-10-27 11:02 UTCEchelonGraph re-scored
  23. 2026-10-27 11:02 UTCVendor advisory
  24. 2026-10-27 11:02 UTCGHSA enrichmentGHSA-frr2-5qjr-h4hw · GitHub severity HIGH · GitHub CVSS 7.5
  25. 2026-10-26 16:31 UTCEPSS rescoreEPSS 1.1% · 64th percentile
Show 74 more
  1. 2026-10-25 16:32 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  2. 2026-10-25 14:40 UTCEchelonGraph re-scored
  3. 2026-10-24 16:32 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  4. 2026-10-23 16:31 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  5. 2026-10-22 16:34 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  6. 2026-10-21 16:32 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  7. 2026-10-20 16:32 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  8. 2026-10-19 16:31 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  9. 2026-10-18 17:28 UTCEchelonGraph re-scored
  10. 2026-10-18 17:28 UTCVendor advisory
  11. 2026-10-18 17:28 UTCGHSA enrichmentGHSA-frr2-5qjr-h4hw · GitHub severity HIGH · GitHub CVSS 7.5
  12. 2026-10-18 16:52 UTCEchelonGraph re-scored
  13. 2026-10-18 16:52 UTCVendor advisory
  14. 2026-10-18 16:51 UTCGHSA enrichmentGHSA-frr2-5qjr-h4hw · GitHub severity HIGH · GitHub CVSS 7.5
  15. 2026-10-18 16:31 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  16. 2026-10-18 03:53 UTCEchelonGraph re-scored
  17. 2026-10-17 16:51 UTCEchelonGraph re-scored
  18. 2026-10-17 16:50 UTCGHSA enrichmentGHSA-frr2-5qjr-h4hw · GitHub severity HIGH · GitHub CVSS 7.5
  19. 2026-10-17 16:33 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  20. 2026-10-16 16:41 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  21. 2026-10-15 16:31 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  22. 2026-10-14 16:32 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  23. 2026-10-13 16:33 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  24. 2026-10-12 16:33 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  25. 2026-10-12 16:19 UTCEchelonGraph re-scored
  26. 2026-10-11 20:01 UTCEchelonGraph re-scored
  27. 2026-10-11 17:14 UTCEchelonGraph re-scored
  28. 2026-10-11 14:46 UTCEchelonGraph re-scored
  29. 2026-10-11 13:48 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  30. 2026-10-11 07:25 UTCOSV refresh
  31. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  32. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  33. 2026-10-08 17:11 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  34. 2026-10-07 23:47 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  35. 2026-10-06 15:17 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  36. 2026-10-05 17:42 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  37. 2026-10-04 23:21 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  38. 2026-10-03 14:25 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  39. 2026-10-01 19:49 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  40. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  41. 2026-09-29 15:21 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  42. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  43. 2026-09-27 13:47 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  44. 2026-09-26 15:58 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  45. 2026-09-26 00:26 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  46. 2026-09-24 14:03 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  47. 2026-09-21 19:49 UTCOSV refresh
  48. 2026-09-20 20:15 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  49. 2026-09-18 19:27 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  50. 2026-09-16 14:07 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  51. 2026-09-16 05:15 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  52. 2026-09-13 16:47 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  53. 2026-09-12 15:01 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  54. 2026-09-11 14:52 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  55. 2026-09-10 09:34 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  56. 2026-09-08 22:00 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  57. 2026-09-07 16:01 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  58. 2026-09-06 13:47 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  59. 2026-09-04 05:06 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  60. 2026-09-02 16:08 UTCOSV refresh
  61. 2026-09-02 14:11 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  62. 2026-09-01 13:53 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  63. 2026-09-01 04:39 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  64. 2026-08-30 19:17 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  65. 2026-08-30 01:22 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  66. 2026-08-28 21:41 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  67. 2026-08-27 14:25 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  68. 2026-08-26 14:46 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  69. 2026-08-25 13:48 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  70. 2026-08-23 00:19 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  71. 2026-08-21 23:49 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  72. 2026-08-20 22:55 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  73. 2026-08-19 17:03 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  74. 2026-08-18 13:48 UTCEPSS rescoreEPSS 1.0% · 60th percentile

Public detection checks

(1 reference)

A public detection check is referenced for this CVE (1 GitHub checker repository). A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code.

  • GitHub checkerBishopFox/CVE-2026-25075-check
    Published Mar 26, 2026
    Open source ↗

Frequently asked(5)

What is CVE-2026-25075?
CVE-2026-25075 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2026-25075 was made public on March 23, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on March 23, 2026. EchelonGraph's copy of the record carries a last-modified date of July 14, 2026; the record at its source may have been updated since.
Is CVE-2026-25075 actively exploited?
CVE-2026-25075 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (65th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-25075?
CVE-2026-25075 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-25075?
A fix for CVE-2026-25075 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-25075 are linked in the Vendor Advisories panel on this page.

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.