CVE-2025-61962
fetchmail: In fetchmail before 6.5.6, the SMTP client can crash when authenticatingupon receiving a 334 status code in a malform...
CVE-2025-61962 is fixed in 3 products on 1 platform, first by fetchmail 6.4.27-1ubuntu0.1, released October 3, 2025. It is not reported as exploited. Patch Radar priority: Routine.
Routine
CVSS
5.9
Medium
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0041
35th percentile
In fetchmail before 6.5.6, the SMTP client can crash when authenticatingupon receiving a 334 status code in a malformed context.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| fetchmail · Debian 14 | 6.5.6-1 | DEBIAN-CVE-2025-61962 | Oct 4, 2025 |
| fetchmail · Ubuntu 22.04.1 LTS (jammy) | 6.4.27-1ubuntu0.1 | fetchmail 6.4.27-1ubuntu0.1 | Oct 3, 2025 |
| fetchmail · Ubuntu 24.04.5 LTS (noble) | 6.4.38-1ubuntu4.1 | fetchmail 6.4.38-1ubuntu4.1 | Oct 3, 2025 |
| fetchmail · Ubuntu 25.04 (plucky) | 6.4.39-1ubuntu0.1 | fetchmail 6.4.39-1ubuntu0.1 | Jan 16, 2026 |
| fetchmail · Ubuntu 25.10 (questing) | 6.5.4-0ubuntu2 | fetchmail 6.5.4-0ubuntu2 | Oct 3, 2025 |
| fetchmail · Ubuntu 26.04.1 LTS (resolute) | 6.5.4-0ubuntu2 | fetchmail 6.5.4-0ubuntu2 | Oct 3, 2025 |
| fetchmail · amzn 2023 | 6.5.7-1.amzn2023 | ALAS2023-2025-1292 | Dec 8, 2025 |
| fetchmail · opensuse-leap 15.6 | 6.4.22-150600.35.3.1 | SUSE-SU-2025:3845-1 | Oct 28, 2025 |
| fetchmail · opensuse-leap 16.0 | 6.5.2-160000.3.1 | OPENSUSE-SU-2026:20432-1 | Mar 26, 2026 |
| fetchmail · sles 15.6 | 6.4.22-150600.35.3.1 | SUSE-SU-2025:3845-1 | Oct 28, 2025 |
| fetchmail · sles 15.7 | 6.4.22-150600.35.3.1 | SUSE-SU-2025:3845-1 | Oct 28, 2025 |
| fetchmail · sles 16.0 | 6.5.2-160000.3.1 | SUSE-SU-2026:20935-1 | Mar 26, 2026 |
| fetchmail-debuginfo · amzn 2023 | 6.5.7-1.amzn2023 | ALAS2023-2025-1292 | Dec 8, 2025 |
| fetchmail-debugsource · amzn 2023 | 6.5.7-1.amzn2023 | ALAS2023-2025-1292 | Dec 8, 2025 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.