Skip to main content
Report · GCP Compute Engine SecurityAbout CVE-2025-0647Published

GCP-2026-004

Source GCP Compute Engine Security

0
Authoritative record:CVE-2025-0647· High 7.9

Not known to be exploited · CVSS 7.9 High.

Data as of 26 Oct 2026, 22:13 UTC

CVSS 3.1 base score
7.9High
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
ArmNeoverse-N2Affected
  • =0
Fixed in–
ArmNeoverse-V3AEAffected
  • =0
Fixed in–
ArmNeoverse-V3Affected
  • =0
Fixed in–
ArmNeoverse-V2Affected
  • =0
Fixed in–
ArmCortex-X925Affected
  • =0
Fixed in–
ArmCortex-X4Affected
  • =0
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.

References

Community reviews

Loading reviews…