CVE-2026-27144 Miscompilation allows memory corruption via CONVNOP-wrapped array copy in cmd/compile

High 7.1 Published Updated

A miscompilation in the Go compiler can cause memory corruption during array copies, potentially allowing attackers to execute arbitrary code or crash applications.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-27144?

CVE-2026-27144 is a high-severity memory corruption vulnerability in Golang Go, published on 8 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

The compiler is meant to unwrap pointers which are the operands of a memory move; a no-op interface conversion prevented the compiler from making the correct determination about non-overlapping moves, potentially leading to memory corruption at runtime.

Weakness: CWE-843

Which versions are affected by CVE-2026-27144?

2 open source packages ship an affected version, including golang and toolchain. It affects 1 product.

PackageAffectedFixed in
golang BitnamiAll versions1.25.9, 1.26.2
toolchain GoAll versions1.25.9, 1.26.2

Products include Golang Go.

How do I fix CVE-2026-27144?

Upgrade golang to a fixed version for your release line: 1.25.9 or 1.26.2.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2026-27144 being exploited?

There is no known exploitation of CVE-2026-27144 in the wild and no public exploit code.

All Golang Go vulnerabilities

Sources

Also known as AZL-98859, BELL-CVE-2026-27144, BIT-golang-2026-27144, CLEANSTART-2026-BL51043, CLEANSTART-2026-KZ49511, CLEANSTART-2026-OE45196 and 641 more.

Is CVE-2026-27144 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free