CVE-2025-61732 | Potential code smuggling via doc comments in cmd/cgo

A discrepancy between how Go and C/C++ comments were parsed allowed for code smuggling into the resulting cgo binary.

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

CVE-2025-61732 is rated Low Risk (38.3/100): CVSS High severity, with low exploitation likelihood (EPSS 0.21%). 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-61732

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.21% +0.19%
2 2026-02-05 — 0.01% —

Full EPSS history (2 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.6 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
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:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
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.
 1.8 6.0 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-61732

OS Trackers for CVE-2025-61732

vendor priority summary link
alpine — CVE-2025-61732: 1 source package rows (go); 92 state rows across 2 repos (3.23-community, edge-community); fixed 2, open 90. https://security.alpinelinux.org/vuln/CVE-2025-61732
debian not yet assigned CVE-2025-61732 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-61732
redhat high — https://access.redhat.com/security/cve/CVE-2025-61732
suse critical CVE-2025-61732 severity critical: SUSE including 101 source package names (2.1.3-6.5:curl-8.14.1-slfo.1.1_3.1, 2.1.3-6.5:iputils-20221126-4.1, …), 427 product×package rows across 53 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/base-os-container, … (53 product lines)): Fixed 338, Known Not Affected 78, First Fixed 11. https://www.suse.com/security/cve/CVE-2025-61732/
ubuntu medium CVE-2025-61732 medium priority: Ubuntu including 7 source packages (golang-1.17, golang-1.20, …), 31 status rows across 5 suites (focal, jammy, noble, questing, upstream): needs-triage 23, DNE 8. https://ubuntu.com/security/CVE-2025-61732

Affected software / configurations for CVE-2025-61732

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

References for CVE-2025-61732

URL Tags
https://go.dev/cl/734220 Patch Product
https://go.dev/issue/76697 Issue Tracking Vendor Advisory
https://groups.google.com/g/golang-announce/c/K09ubi9FQFk Mailing List Release Notes
https://pkg.go.dev/vuln/GO-2026-4433 Vendor Advisory Patch
cvelogic Threat Intelligence