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 determina…

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

1. Apr 8, 2026 · NIST NVD

   Detected

   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.

2. Jul 25, 2026 · NIST NVD

   Updated

   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.

Affected

• cpe golang/goversion unspecified

Sources

• CVE.orgVulnerability recordCVE-2026-27144

  Official CVE identifier

  cve.org
• NIST NVDVulnerability recordCVE-2026-27144

  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.

  nvd.nist.gov

References

• Patch · go.dev
• Issue Tracking · go.dev
• Mailing List · groups.google.com
• Vendor Advisory · pkg.go.dev