CVE-2026-121207

Description

An uninitialized resource flaw was found in the Dawn component of the Chromium browser.

Upstream bug(s):

https://issues.chromium.org/issues/563359278

Statement

Red Hat Product Security rates the severity of this flaw as determined by the Google Chrome Security Advisory.

Mitigation

--- CME Mitigation Guidance (2026-11-06) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to ensure complete initialization of Dawn WebGPU resources before processing untrusted web content across the sandbox boundary: upgrade to Google Chrome 157.0.8103.38 (or the fixed Chromium builds), which properly initializes Dawn resources to prevent unauthorized memory reads outside the sandbox, closing crafted HTML page. Until patched, this is only a concern on macOS users running Google Chrome prior to version 157.0.8103.38 — non-macOS platforms are unaffected — so restrict user navigation to untrusted web pages and monitor browser processes for unexpected activity. As a compensating measure, deploy EDR monitoring to detect anomalous process execution and post-exploitation behavior if memory disclosure is chained into a sandbox escape. These controls limit blast radius and contain exploitation, but they do not fix the underlying uninitialized resource defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory; Read Application Data

When reusing a resource such as memory or a program variable, the original contents may not have been cleared before it is sent to an untrusted party.

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Instability

The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend, possibly leading to a crash.

Other

Technical Impact: Unexpected State; Varies by Context

The consequences vary depending on the type of resource and how it is used within the product.

Frequently Asked Questions

Want to get errata notifications? Sign up here.