CVE-2026-121037
Description
An out of bounds write flaw was found in the ANGLE component of the Chromium browser.
Upstream bug(s):
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-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 prevent out-of-bounds memory writes within the ANGLE graphics abstraction layer during web rendering: upgrade to Google Chrome 157.0.8103.38 (or the fixed Chromium builds), which corrects memory bounds validation within the ANGLE graphics abstraction layer, closing crafted HTML page rendering graphics via ANGLE. Until patched, this is only a concern on Chromium installations on Windows — Linux and macOS deployments are unaffected — so restrict user browsing to trusted internal destinations and block navigation to untrusted or unknown external web pages. As a compensating measure, enable address space layout randomization to impede reliable memory address calculation, enforce control flow integrity to validate indirect call targets against hijacked function pointers in ANGLE, enable arbitrary code guard to prevent allocating or converting writable memory into executable code, deploy Windows Defender Application Control in enforced mode to block unauthorized binaries dropped after sandbox escape, deploy endpoint detection and response to monitor and alert on anomalous post-escape process behavior, and enforce non-executable memory protections via the NX/XD bit to block shellcode execution in corrupted data structures. These controls limit blast radius and contain exploitation, but they do not fix the underlying out-of-bounds write defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-101 ASLR (Address Space Layout Randomization) (medium)
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 8.8 | N/A | 9.6 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | Required | N/A | Required |
| Scope | Unchanged | N/A | Changed |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.
Other
Technical Impact: Unexpected State
Subsequent write operations can produce undefined or unexpected results.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
