GCP-2026-004
Source GCP Compute Engine Security
Not known to be exploited · CVSS 7.9 High.
Data as of 26 Oct 2026, 22:13 UTC
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 14 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ArmNeoverse-N2 | Affected
| Fixed in– |
| ArmNeoverse-V3AE | Affected
| Fixed in– |
| ArmNeoverse-V3 | Affected
| Fixed in– |
| ArmNeoverse-V2 | Affected
| Fixed in– |
| ArmCortex-X925 | Affected
| Fixed in– |
| ArmCortex-X4 | Affected
| Fixed in– |
AI-suggested
No customer action is required as Google has already applied mitigations to the Google Cloud Arm server fleet to address this vulnerability.
Description
A vulnerability in the CPP RCTX instruction on select Arm processors used in Google Cloud Compute Engine Arm VMs (C4A, A4X) allows an attacker with privileged guest kernel access to inhibit TLB invalidations. This can potentially enable unauthorized reading of sensitive data. Google has already applied mitigations to the affected Arm server fleet, and no customer action is required.