CVE-2026-27143 is a vulnerability in the Go compiler's cmd/compile component caused by incorrect bounds-check elimination for loop induction variables. During optimization, the compiler could incorrectly prove that slice or array accesses indexed by a mutated induction variable were always in bounds, while failing to account for integer overflow or underflow of that variable relative to the loop condition. If the induction variable wrapped, the generated code could perform invalid indexing at runtime and access memory outside the original slice or array bounds, potentially resulting in memory corruption. The issue affects Go releases up to 1.26.1 and was addressed in Go 1.26.2 and 1.25.9 by ensuring that mutated induction variables that can overflow or underflow are not used for bounds-check elimination.
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.
26 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Go compiler vulnerability that can lead to possible memory corruption after bounds check elimination.
A Go cmd/compile vulnerability that can lead to possible memory corruption after bounds check elimination.
A Go cmd/compile vulnerability that can lead to possible memory corruption after bound check elimination.
A Go compiler vulnerability in cmd/compile that can lead to possible memory corruption after bounds check elimination.
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.