CVE-2026-106370: Uninitialized resource in GPU

Published May 27, 2026
·
Updated

Chromium CVE-2026-106370: Uninitialized resource

Other sources

This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.

— Microsoft

Uninitialized resource in GPU in Google Chrome on on Android prior to 155.0.8059.39 allowed a remote attacker who had compromised the renderer process to read memory outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

— MITRE

Credit

Google

Affected Software

4 affected componentsFixes available
Google Chrome<155.0.8059.39
155.0.8059.39
All of the following
Google Chrome<155.0.8059.39
Google Android
Microsoft Edge (Chromium-based)<155.0.4283.45
155.0.4283.45

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 155.0.8059.39
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 155.0.4283.45
  3. Upgrade

    Upgrade Google Chrome on Android to a version that resolves this vulnerability.

    Fixed in 155.0.8059.39

Event History

May 27, 2026
CVE Published
12:00 AM
Data Sourced
12:00 AM
SeverityWeaknessAffected Software
Oct 6, 2026
CVE Published
via MITRE·06:41 PM
Data Sourced
via MITRE·06:41 PM
DescriptionWeakness
Data Sourced
via NVD·07:18 PM
DescriptionSeverityWeaknessAffected Software
Oct 16, 2026
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

Who is exposed to this issue?

Google Chrome on Android versions earlier than 155.0.8059.39 are affected. Exploitation requires that the attacker has already compromised the renderer process.

2

Can a crafted web page exploit this issue by itself?

No. The issue can be triggered through a crafted HTML page only after the renderer process has been compromised, and it may allow reading memory outside the sandbox.

3

What should teams do if they cannot patch immediately?

The provided information does not identify a workaround or mitigation. Prioritize updating affected Android Chrome installations to 155.0.8059.39 or later.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203