Loading vulnerability…
CVE-2026-27140 is a trust-layer bypass in Go's cmd/go build tooling involving specially crafted SWIG file names containing 'cgo' and associated payloads. The flaw enables code smuggling and arbitrary code execution during builds. Exploitation targets the build environment rather than requiring execution of the resulting application. Exact affected upstream Go versions and the vulnerable function are not specified.
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.
75 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Go build-time trust-layer bypass involving specially crafted SWIG filenames and payloads can permit arbitrary code execution. The advisory lists a patch publication date but cautions that updated CGSL packages may not yet be available.
A vulnerability addressed by an AlmaLinux 9.2 security update; the notice rates the associated vendor severity as Important.
An arbitrary code execution vulnerability in Go/cmd/go triggered via malicious SWIG file names.
An arbitrary code execution vulnerability in Go/cmd/go triggered via malicious SWIG file names.
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.