Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Go cmd/compile no-op interface conversion bypasses overlap checking

IdentifiersCVE-2026-27144CWE-119

CVE-2026-27144 is a vulnerability in the Go compiler (cmd/compile) in which the compiler failed to unwrap pointers contained within a no-op interface conversion when determining whether a memory move was non-overlapping. As a result, code patterns involving assignments such as composite-value moves could be misclassified as safe non-overlapping copies even when the source and destination memory regions could overlap. This caused the compiler to select an unsafe move path instead of a careful copy path for overlapping composite values, potentially introducing memory corruption at runtime in programs written in otherwise safe Go code. The fix changes the compiler to unwrap all such no-op interface conversions before deciding whether a move is non-overlapping.

Share:
For your environment

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.

ANALYST BRIEF

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.

Successful exploitation can break Go's memory-safety guarantees and lead to runtime memory corruption. Reported consequences include out-of-bounds access and control-flow hijacking potential arising from incorrect compiler-generated move operations. The issue affects compiled program behavior rather than a library API boundary, so vulnerable binaries may exhibit unsafe memory operations even when the source code uses only safe Go constructs.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, reduce exposure by avoiding deployment of binaries built with vulnerable Go compiler versions where untrusted input can influence code paths involving composite-value moves and aliasing-sensitive assignments. Because this is a compiler defect in generated code, practical mitigation short of upgrading is limited; the reliable mitigation is to rebuild with a patched compiler. Review and prioritize binaries built with vulnerable Go versions, especially those handling attacker-controlled data in memory-sensitive paths.

Remediation

Patch, then assume compromise.

Upgrade to a fixed Go release. The provided context states that Go 1.26.2 and Go 1.25.9 include the fix for CVE-2026-27144, and affected releases included versions up to 1.26.1. Rebuild affected applications with a patched Go toolchain so the corrected compiler logic is applied.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

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.

VendorProductType
GolangGoapplication
GolangGolangapplication
Rocky LinuxDelveapplication
Rocky LinuxGolangapplication
Rocky LinuxModule.Delveapplication
Rocky LinuxModule.Golangapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity11

Community discussion across Reddit, Mastodon, and other social sources.