CVE-2025-61732
Code smuggling in cgo due to Go vs C/C++ comment parsing discrepancy.
Is CVE-2025-61732 being exploited?
Not confirmed. CVE-2025-61732 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.48% probability of exploitation in the next 30 days.
How severe is CVE-2025-61732?
CVE-2025-61732 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-61732?
Yes. A fix has been recorded for CVE-2025-61732. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What should I do about CVE-2025-61732?
Update toolchains when patched; monitor builds for tampering.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Code injection leading to arbitrary code execution via smuggled C/C++ code in cgo binaries.
Patch when possible
- affected< 1.24.13
- affected>= 1.25.0-0 and < 1.25.7
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.