LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 8.6Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-61732 is a Go toolchain flaw in cmd/cgo where documentation comments could be interpreted differently by Go and C/C++. Under affected conditions, hidden code could be included in a compiled cgo binary. The business risk is strongest for teams building cgo code from third-party or untrusted sources.

Executive priority

Treat this as a high-priority build-chain issue, not a broad internet-facing emergency. Prioritize teams compiling Go with cgo, especially where third-party code enters automated builds or product release pipelines.

Technical view

The source bundle describes a comment-parsing discrepancy in cmd/cgo that allowed code smuggling into the resulting cgo binary. It is classified as CWE-94 with CVSS 3.1 score 8.6, local attack vector, user interaction required, changed scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely in Go build environments using cgo, especially CI/CD pipelines, package build systems, developer workstations, and vendors rebuilding third-party Go code. The bundle lists Go toolchain cmd/cgo as affected and includes Red Hat advisories, but product-specific exposure must be confirmed from vendor guidance.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation evidence. Exploitation appears to require a victim to build affected source with cgo, so this is more supply-chain and build-time risk than remote network exposure.

Researcher notes

Key unknowns from the bundle are exact fixed upstream versions and downstream package status beyond linked vendor advisories. Avoid claiming exploitation in the wild; KEV is false. Validation should focus on cgo usage, toolchain provenance, and vendor-specific package fixes.

Mitigation direction

  • Review Go advisory GO-2026-4433 for fixed Go versions and upgrade guidance.
  • Apply relevant vendor updates, including applicable Red Hat security advisories.
  • Reduce or isolate builds of untrusted Go source that uses cgo.
  • Pin trusted dependencies and review source provenance in CI/CD pipelines.
  • Check vendor guidance before assuming downstream products are affected or fixed.

Validation and detection

  • Inventory Go toolchain versions used by developers, CI, and release builders.
  • Identify repositories and build jobs that enable or require cgo.
  • Check whether installed Red Hat packages match the listed RHSA fixes.
  • Confirm builds are using patched Go toolchains after remediation.
  • Review dependency intake controls for untrusted cgo-containing source.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-61732 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
38Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.6CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H1.86CISA-ADP
7.4CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N2.25.2redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

8.6High
CVSS 3.1 vector shape for CVE-2025-61732Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
redhat-SADPcmd/cgo: Go cgo: Code smuggling due to comment parsing discrepancy
other:Red Hat severity ratingcvssV3_1
  • 2026-02-05T05:00:47.678Z: Reported to Red Hat.
  • 2026-02-05T03:42:26.392Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Go toolchaincmd/cgocmd/cgo, 0, 1.25.0-0unaffected
Weakness

CWE details

CWE-94

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs