Memory corruption via unsound loop bound elimination
Published Apr 8, 2026 · Updated Apr 8, 2026
Integer overflow in Go compile command before 1.25.9 and 1.26.0-0 through 1.26.1 allows attackers to cause memory corruption. During loop bound-check elimination, the compiler can incorrectly prove slice or array indexing by a mutated induction variable to be in bounds without excluding arithmetic underflow or overflow. Reachability requires compiling and running code whose loop condition permits that induction variable to wrap, after which the generated program can access memory beyond the original slice or array.
Summary
What happened
Integer overflow in Go compile command before 1.25.9 and 1.26.0-0 through 1.26.1 allows attackers to cause memory corruption. During loop bound-check elimination, the compiler can incorrectly prove slice or array indexing by a mutated induction variable to be in bounds without excluding arithmetic underflow or overflow. Reachability requires compiling and running code whose loop condition permits that induction variable to wrap, after which the generated program can access memory beyond the original slice or array.
The record
- CVE
- CVE-2026-27143
- Published
- Apr 8, 2026
- Updated
- Apr 8, 2026
- Vendor
- Go
- Product
- compile command
- Classifications
- CWE-190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 8, 2026CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.25.9
- Affected versionversion=1.26.0-0 <1.26.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo