Skip to main content

Google Chrome CVE-2026-13923

| EUVDEUVD-2026-40609 MEDIUM
Use of Uninitialized Variable (CWE-457)
2026-06-30 chrome-cve-admin@google.com GHSA-4w24-9gxj-7vcf
6.5
CVSS 3.1 · Vendor: google
Share

Severity by source

Vendor (google) PRIMARY
6.5 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
vuln.today AI
6.5 MEDIUM

Delivered via crafted web page over network (AV:N/AC:L/PR:N), requires user to visit the page (UI:R), impacts only confidentiality with no integrity or availability effect (C:H/I:N/A:N).

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
SUSE
MEDIUM
qualitative
Red Hat
6.5 MEDIUM
qualitative

Primary rating from Vendor (google).

CVSS VectorVendor: google

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

4
Analysis Generated
Jul 01, 2026 - 02:28 vuln.today
CVSS changed
Jul 01, 2026 - 02:22 NVD
6.5 (MEDIUM)
CVE Published
Jun 30, 2026 - 23:17 cve.org
UNKNOWN (no severity yet)
CVE Published
Jun 30, 2026 - 23:17 cve.org
MEDIUM 6.5

DescriptionCVE.org

Uninitialized Use in GPU in Google Chrome on Android prior to 150.0.7871.47 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)

AnalysisAI

Uninitialized GPU memory use in Google Chrome on Android prior to 150.0.7871.47 allows a remote attacker to read potentially sensitive data from process memory by luring a user to a crafted HTML page. The flaw (CWE-457) is confined to the Android GPU code path and requires only user interaction to trigger, with CVSS confirming unauthenticated network delivery and High confidentiality impact. No public exploit code or active exploitation via CISA KEV has been identified at time of analysis; Google has released a fix in stable channel version 150.0.7871.47.

Technical ContextAI

CWE-457 (Use of Uninitialized Variable) arises when a memory region in the GPU process is accessed before it has been properly zeroed or set. In Chrome's multi-process sandbox architecture, the GPU process handles hardware-accelerated rendering separately from the renderer process; on Android, when parsing or rendering attacker-controlled HTML content, certain GPU memory regions may be read while still containing residual data from prior allocations. This residual data - potentially credentials, tokens, or other in-memory artifacts - could then be exposed to the renderer or to script running in the attacker's page context. The EUVD entry EUVD-2026-40609 narrows the affected range to Chrome versions below 150.0.7871.47 specifically on Android; desktop Chrome platforms are not listed as affected by this particular GPU code path.

RemediationAI

Vendor-released patch: 150.0.7871.47. Users should update Google Chrome on Android to version 150.0.7871.47 or later via the Google Play Store; Chrome typically auto-updates, but users should confirm the installed version under Settings > About Chrome. The advisory is available at chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. No documented workaround is confirmed in the available data; disabling hardware acceleration via chrome://flags/#disable-accelerated-2d-canvas could theoretically reduce GPU code surface but would degrade rendering performance and is not an officially documented mitigation - this trade-off is generally not warranted given the straightforward availability of the patch.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Package Hub 15 SP7 Fixed
openSUSE Tumbleweed Fixed
SUSE Package Hub 15 SP7 Affected

Share

CVE-2026-13923 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy