CVE-2026-121156
개요
A buffer overflow flaw was found in the Dawn component of the Chromium browser.
Upstream bug(s):
내용
Red Hat Product Security rates the severity of this flaw as determined by the Google Chrome Security Advisory.
완화 방법
--- CME Mitigation Guidance (2026-11-04) ---
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 eliminate heap memory corruption in the Dawn component to prevent arbitrary code execution outside the browser sandbox: upgrade to Chromium 157.0.8103.38+ (or the fixed Chromium builds), which fixes heap buffer bounds handling in the Dawn component to prevent out-of-bounds memory writes, closing crafted HTML page. Until patched, this is a concern on Chromium and Google Chrome installations across all platforms, so Restrict user interaction with untrusted websites and avoid navigating to unverified external web pages. As a compensating measure, Enable ASLR to randomize Chromium process memory layout, requiring attackers to locate an information leak for reliable execution, Deploy EDR agents to detect anomalous process execution and post-exploitation activity following a sandbox escape, and Enforce NX/XD bit non-executable memory permissions on the heap to prevent shellcode execution. These controls limit blast radius and contain exploitation, but they do not fix the underlying heap buffer overflow defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-101 ASLR (Address Space Layout Randomization) (medium)
취약점 이해 (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory)
Buffer overflows generally lead to crashes. Other attacks leading to lack of availability are possible, including putting the program into an infinite loop.
Integrity,Confidentiality,Availability,Access Control
Technical Impact: Execute Unauthorized Code or Commands; Bypass Protection Mechanism; Modify Memory
Buffer overflows often can be used to execute arbitrary code, which is usually outside the scope of a program's implicit security policy. Besides important user data, heap-based overflows can be used to overwrite function pointers that may be living in memory, pointing it to the attacker's code. Even in applications that do not explicitly use function pointers, the run-time will usually leave many in memory. For example, object methods in C++ are generally implemented using function pointers. Even in C programs, there is often a global offset table used by the underlying runtime.
Integrity,Confidentiality,Availability,Access Control,Other
Technical Impact: Execute Unauthorized Code or Commands; Bypass Protection Mechanism; Other
When the consequence is arbitrary code execution, this can often be used to subvert any other security service.
