CVE-2025-61729 | Excessive resource consumption when printing error string for host certificate validation in crypto/x509

Within HostnameError.Error(), when constructing an error string, there is no limit to the number of hosts that will be printed out. Furthermore, the error string is constructed by repeated string concatenation, leading to quadratic runtime. Therefore, a certificate provided by a malicious actor can result in excessive resource consumption.

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

CVE-2025-61729 is rated Moderate Risk (42.9/100): CVSS High severity, with low exploitation likelihood (EPSS 0.45%). Review affected assets and schedule remediation.

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-61729

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.01% 0.45% +0.44%
2 2025-12-03 — 0.01% —

Full EPSS history (2 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/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: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:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-61729

OS Trackers for CVE-2025-61729

vendor priority summary link
alpine — CVE-2025-61729: 3 source package rows (docker, go, rclone); 150 state rows across 3 repos (3.22-community, 3.23-community, edge-community); fixed 6, open 144. https://security.alpinelinux.org/vuln/CVE-2025-61729
debian not yet assigned CVE-2025-61729 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-61729
redhat high — https://access.redhat.com/security/cve/CVE-2025-61729
suse high CVE-2025-61729 severity important: SUSE including 169 source package names (13.2-9.2:curl-8.14.1-slfo.1.1_3.1, 13.2-9.2:iputils-20221126-6.1, …), 605 product×package rows across 71 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/base-os-container, … (71 product lines)): Fixed 444, Known Not Affected 147, First Fixed 14. https://www.suse.com/security/cve/CVE-2025-61729/
ubuntu medium CVE-2025-61729 medium priority: Ubuntu including 2 source packages (golang-1.24, golang-1.25), 10 status rows across 5 suites (jammy, noble, plucky, questing, upstream): needs-triage 6, DNE 3, ignored 1. https://ubuntu.com/security/CVE-2025-61729

Affected software / configurations for CVE-2025-61729

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

References for CVE-2025-61729

cvelogic Threat Intelligence