Vulnary
← back to the feed
Critical· 9.8

CVE-2026-27143

A flaw in the Go compiler's handling of arithmetic on loop induction variables can allow underflow or overflow to go unchecked, enabling invalid array indexing at runtime and possible memory corruption. The vulnerability is rated critical with a CVSS base score of 9.8. It affects the golang go product, and there is currently no known exploitation or public exploit.

publishedApr 8, 2026
last modifiedJul 25, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
42th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 8, 2026

No official fix yet. If none appears within 45 days of first tracking, this entry is removed automatically.

01

Who is affected

golang go

02

Real-world impact

Memory corruption could lead to crashes, data corruption, or arbitrary code execution.

03

Why this severity

CVSS 9.8 (Critical) reflects network‑attackable, low‑complexity impact with no privileges or user interaction required.

04

What to do about it

no official fix yet

No official fix or mitigation is documented in the sources yet. Monitor the vendor advisory and apply the patch as soon as it is released.

No fix documented in sources

05

Timeline

  1. Apr 8, 2026 · Apr 8, 2026
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 25, 2026 · 11d ago
    Advisory updated
    The NVD record was last revised.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →