CVE-2025-61962

In fetchmail before 6.5.6, the SMTP client can crash when authenticating upon receiving a 334 status code in a malformed context.

Published: 2025-10-03 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-61962 is rated Low Risk (34.1/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.38%). 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-61962

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-06-15 0.06% 0.38% +0.32%
2 2026-03-14 0.04% 0.06% +0.02%
3 2026-03-02 — 0.04% —

Full EPSS history (5 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.9 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/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:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.2 3.6 [email protected]

Weakness enumeration for CVE-2025-61962

OS Trackers for CVE-2025-61962

vendor priority summary link
alpine medium CVE-2025-61962: 1 source package rows (fetchmail); 10 state rows across 2 repos (3.22-community, edge-community); fixed 0, open 10. https://security.alpinelinux.org/vuln/CVE-2025-61962
debian not yet assigned CVE-2025-61962 not yet assigned priority: Debian including 1 source packages (fetchmail), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2025-61962
redhat medium — https://access.redhat.com/security/cve/CVE-2025-61962
suse medium — https://www.suse.com/security/cve/CVE-2025-61962/
ubuntu medium CVE-2025-61962 medium priority: Ubuntu including 1 source packages (fetchmail), 8 status rows across 8 suites (bionic, focal, jammy, noble, plucky, questing, upstream, xenial): released 5, needs-triage 3. https://ubuntu.com/security/CVE-2025-61962

Affected software / configurations for CVE-2025-61962

Vendor Product Version Raw CPE
fetchmail fetchmail >= 5.9.9, < 6.5.6 cpe:2.3:a:fetchmail:fetchmail:*:*:*:*:*:*:*:*

References for CVE-2025-61962

cvelogic Threat Intelligence