Arbitrary Code Execution in Go cmd/go via malicious SWIG file names
CVE-2026-27140 is a build-time arbitrary code execution vulnerability in the Go toolchain, specifically in cmd/go's handling of SWIG source files in conjunction with cgo. A specially crafted SWIG source file can exploit a file-naming convention that is trusted within the cgo compiler trust boundary. By smuggling attacker-controlled input through this trusted naming path, an attacker can bypass the intended trust layer and cause arbitrary code to execute during the build process. The issue is a supply-chain and developer-environment risk affecting builds that process malicious SWIG inputs rather than a runtime flaw in compiled Go applications.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
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.
Recent activity
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
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.