PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-9912 Google CVE debrief

CVE-2026-9912 is an information disclosure vulnerability in Google Chrome on Android, rated High severity by Chromium. The flaw stems from inappropriate implementation in the GPU component, allowing a remote attacker to extract potentially sensitive information from process memory by enticing a user to visit a crafted HTML page. The vulnerability affects Chrome on Android versions prior to 148.0.7778.216. Google addressed this issue in the stable channel update released May 28, 2026. No known exploitation in ransomware campaigns has been reported.

Vendor
Google
Product
Chrome
CVSS
MEDIUM 6.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-05-28
Original CVE updated
2026-05-29
Advisory published
2026-05-28
Advisory updated
2026-05-29

Who should care

Android users running Chrome versions prior to 148.0.7778.216; mobile security teams; organizations with BYOD Android deployments; developers of Android-based enterprise solutions

Technical summary

The vulnerability exists in the GPU implementation of Google Chrome on Android, where improper handling of GPU operations allows memory contents to be exposed to attacker-controlled web content. By crafting a malicious HTML page, a remote attacker can trigger the flaw to read sensitive data from the browser's process memory. This represents a significant privacy and security risk as process memory may contain credentials, session tokens, or other confidential information. The fix in Chrome 148.0.7778.216 corrects the GPU implementation to prevent unauthorized memory access.

Defensive priority

high

Recommended defensive actions

  • Update Chrome on Android to version 148.0.7778.216 or later through Google Play or system updates
  • Verify Chrome version via Settings > About Chrome and confirm update installation
  • For managed Android devices, enforce minimum Chrome version via enterprise mobility management (EMM) policies
  • Monitor for unexpected GPU process crashes or memory-related anomalies in Chrome as potential exploitation indicators
  • Review web traffic logs for visits to untrusted or newly registered domains that may serve crafted HTML content
  • Apply principle of least privilege for Android applications to limit impact of browser-based memory disclosure
  • Consider enabling site isolation features in Chrome if not already active to reduce cross-site memory exposure

Evidence notes

CVE description confirms GPU implementation flaw in Chrome Android; Chrome Releases blog and Chromium issue tracker provide vendor acknowledgment. No CVSS vector available in source data; severity derived from Chromium-assigned 'High' rating.

Official resources

2026-05-28