CVE-2026-95357Public exploitNetwork attack vector

GPU-process memory corruption via 3D texture depth

Published Sep 29, 2026 · Updated Sep 29, 2026

Out-of-bounds write in Google Chrome on Android before 154.0.8037.57 allows remote attackers to corrupt GPU-process memory via a crafted page. A WebGL 3D-texture depth increase reaches the Qualcomm Adreno driver, where a negative value causes an out-of-bounds write; Chrome's GPU decoder previously allowed the call instead of losing the GL context. Exploitation requires the victim to open attacker-controlled content on an affected Android device with the Qualcomm driver; the demonstrated failure crashes the GPU process, while code execution outside the sandbox is the reported security impact.

CVSS severityUnavailable
Unscored
EPSS probability0.47%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Out-of-bounds write in Google Chrome on Android before 154.0.8037.57 allows remote attackers to corrupt GPU-process memory via a crafted page. A WebGL 3D-texture depth increase reaches the Qualcomm Adreno driver, where a negative value causes an out-of-bounds write; Chrome's GPU decoder previously allowed the call instead of losing the GL context. Exploitation requires the victim to open attacker-controlled content on an affected Android device with the Qualcomm driver; the demonstrated failure crashes the GPU process, while code execution outside the sandbox is the reported security impact.

The record

CVE
CVE-2026-95357
Published
Sep 29, 2026
Updated
Sep 29, 2026
Vendor
WebM Project
Product
Google Chrome
Classifications
T1189
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Sep 29, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 29, 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.

  1. Affected versionversion=154.0.8037.57 <154.0.8037.57

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

WebM Project · Google Chromeversion=154.0.8037.57 <154.0.8037.57

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

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.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

T1189Drive-by Compromise

Public exploit references

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

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started