CVE-2026-121249
Description
A buffer overflow 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 compile and run Chromium with compiler stack canaries enabled to abort execution before ANGLE stack buffer corruption diverts control flow: upgrade to Google Chrome 157.0.8103.38 (or the fixed Chromium builds), which details are restricted upstream; remediates the out-of-bounds write defect within the ANGLE graphics engine, closing crafted HTML page. Until patched, this is a concern on all platforms running Chromium-based browsers rendering untrusted web content, so restrict user browsing and block access to untrusted or unverified web pages. As a compensating measure, compile with FORTIFY_SOURCE to detect and abort on out-of-bounds writes during standard library memory operations, monitor endpoint detection and response telemetry for anomalous child process spawning and post-exploitation behavior escaping the browser sandbox, enable address space layout randomization across system binaries to impede ROP gadget resolution, and enforce NX/XD bit non-executable memory protection to prevent execution of injected shellcode on the stack. These controls limit blast radius and contain exploitation, but they do not fix the underlying stack-based buffer overflow — apply the upstream patch to fully remediate.
Highest-impact CME: CME-103 Stack Canaries (Stack Protector) (high)
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)
Availability
Technical Impact: Modify Memory; 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: Modify Memory; Execute Unauthorized Code or Commands; Bypass Protection Mechanism
Buffer overflows often can be used to execute arbitrary code, which is usually outside the scope of a program's implicit security policy.
Integrity,Confidentiality,Availability,Access Control,Other
Technical Impact: Modify Memory; 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.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
