Loading vulnerability…
CVE-2025-61732 is a vulnerability in Go's cmd/cgo caused by a discrepancy between how Go documentation comments and C/C++ comments are parsed. In cgo-enabled source, specially crafted doc comments can be interpreted differently by the Go toolchain and the downstream C/C++ compilation path, allowing attacker-controlled content to be smuggled into the generated cgo output and ultimately into the resulting binary. The issue is rooted in inconsistent parsing semantics across language boundaries during code generation, creating an opportunity for unintended native code to be incorporated into build artifacts.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
32 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability in Go's cmd/cgo component involving potential code smuggling through documentation comments.
A cmd/cgo vulnerability in golang involving potential code smuggling through doc comments.
A cmd/cgo vulnerability in golang involving potential code smuggling via documentation comments.
A vulnerability in Go cmd/cgo involving potential code smuggling via documentation comments.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.