CVE-2025-61724 | Excessive CPU consumption in Reader.ReadResponse in net/textproto

The Reader.ReadResponse function constructs a response string through repeated string concatenation of lines. When the number of lines in a response is large, this can cause excessive CPU consumption.

Published: 2025-10-29 Last update: 2026-01-29 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

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

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 2025-11-21 0.05% 0.02% -0.03%
2 2025-11-04 0.02% 0.05% +0.03%
3 2025-10-30 — 0.02% —

Full EPSS history (3 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L 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:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
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:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 3.9 1.4 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-61724

OS Trackers for CVE-2025-61724

vendor priority summary link
alpine — CVE-2025-61724: 1 source package rows (go); 85 state rows across 2 repos (3.22-community, edge-community); fixed 2, open 83. https://security.alpinelinux.org/vuln/CVE-2025-61724
debian not yet assigned CVE-2025-61724 not yet assigned priority: Debian including 4 source packages (golang-1.15, golang-1.19, golang-1.24, golang-1.25), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2025-61724
redhat medium — https://access.redhat.com/security/cve/CVE-2025-61724
suse medium CVE-2025-61724 severity moderate: SUSE including 77 source package names (2.2.0-3.1:curl-8.14.1-slfo.1.1_3.1, 2.2.0-3.1:libcurl4-8.14.1-slfo.1.1_3.1, …), 495 product×package rows across 69 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/base-os-container, … (69 product lines)): Fixed 440, Known Not Affected 41, First Fixed 14. https://www.suse.com/security/cve/CVE-2025-61724/
ubuntu medium CVE-2025-61724 medium priority: Ubuntu including 16 source packages (golang, golang-1.10, …), 98 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): needs-triage 49, DNE 47, ignored 2. https://ubuntu.com/security/CVE-2025-61724

Affected software / configurations for CVE-2025-61724

Vendor Product Version Raw CPE
golang go < 1.24.8 cpe:2.3:a:golang:go:*:*:*:*:*:*:*:*
golang go >= 1.25.0, < 1.25.2 cpe:2.3:a:golang:go:*:*:*:*:*:*:*:*

References for CVE-2025-61724

cvelogic Threat Intelligence