CVE-2025-62291

In the eap-mschapv2 plugin (client-side) in strongSwan before 6.0.3, a malicious EAP-MSCHAPv2 server can send a crafted message of size 6 through 8, and cause an integer underflow that potentially results in a heap-based buffer overflow.

Published: 2026-01-16 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-62291 is rated Low Risk (34.4/100): CVSS High severity, with low exploitation likelihood (EPSS 0.02%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-62291

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-02-18 0.06% 0.02% -0.03%
2 2026-01-22 0.04% 0.06% +0.01%
3 2026-01-17 0.04%

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-62291

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.1 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
2.2 5.9 [email protected]

Weakness enumeration for CVE-2025-62291

OS Trackers for CVE-2025-62291

vendor priority summary link
alpine CVE-2025-62291: 1 source package rows (strongswan); 57 state rows across 6 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, 3.23-main, edge-main); fixed 6, open 51. https://security.alpinelinux.org/vuln/CVE-2025-62291
debian not yet assigned CVE-2025-62291 not yet assigned priority: Debian including 1 source packages (strongswan), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-62291
redhat high https://access.redhat.com/security/cve/CVE-2025-62291
suse high CVE-2025-62291 severity important: SUSE including 53 source package names (strongswan, strongswan-5.1.3-26.29.1, …), 188 product×package rows across 38 product lines (SUSE Enterprise Storage 7.1, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (38 product lines)): Fixed 150, Known Not Affected 31, First Fixed 7. https://www.suse.com/security/cve/CVE-2025-62291/
ubuntu medium CVE-2025-62291 medium priority: Ubuntu including 1 source packages (strongswan), 9 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): needs-triage 5, released 4. https://ubuntu.com/security/CVE-2025-62291

Affected software / configurations for CVE-2025-62291

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-62291

cvelogic Threat Intelligence