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

High 8.6 Published Updated

Attackers can smuggle malicious code into cgo binaries via doc comments, potentially leading to code execution during compilation.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2025-61732?

CVE-2025-61732 is a high-severity code injection vulnerability in Golang Go, published on 5 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

Official description

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

Weakness: CWE-94

Which versions are affected by CVE-2025-61732?

2 open source packages ship an affected version, including golang and toolchain. It affects 1 product.

PackageAffectedFixed in
golang BitnamiAll versions1.24.13, 1.25.7
toolchain GoAll versions1.24.13, 1.25.7
Linux distribution packages (2)
go1.24 openSUSE:TumbleweedAll versions1.24.13-1.1
go1.25 openSUSE:TumbleweedAll versions1.25.7-1.1

Products include Golang Go.

How do I fix CVE-2025-61732?

Upgrade golang to a fixed version for your release line: 1.24.13 or 1.25.7.

Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.

Is CVE-2025-61732 being exploited?

There is no known exploitation of CVE-2025-61732 in the wild and no public exploit code.

All Golang Go vulnerabilities

Sources

Also known as AZL-76688, AZL-76743, AZL-78937, AZL-98736, BELL-CVE-2025-61732, BIT-golang-2025-61732 and 469 more.

Is CVE-2025-61732 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free