CVE-2026-121229
説明
A memory corruption flaw was found in the ANGLE 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 prevent rendering of untrusted web content or isolate the Chromium GPU process to limit memory corruption within the ANGLE graphics abstraction layer: upgrade to Google Chrome 157.0.8103.38 (or the fixed Chromium builds), which vendor restricted specific bug details; resolves memory corruption within the ANGLE component, closing crafted HTML page. Until patched, this is a concern on Chromium deployments across all supported operating systems, so Restrict users from browsing untrusted sites or opening untrusted HTML pages that trigger ANGLE graphics processing. As a compensating measure, Enforce Address Space Layout Randomization to hinder reliable code-reuse attacks against the ANGLE userspace process, Enable the NX/XD bit to prevent execution of injected shellcode in corrupted data memory regions, Enforce full RELRO and PIE to ensure a read-only Global Offset Table and randomized binary code addresses, Enable Control Flow Integrity and Shadow Call Stack to validate indirect calls and return addresses in ANGLE, Apply kernel-level seccomp syscall filtering to constrain system calls accessible to compromised browser or GPU processes, and Deploy EDR agents to monitor for anomalous process activity and post-exploitation behavior escaping the sandbox. These controls limit blast radius and contain exploitation, but they do not fix the underlying memory corruption defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-601 Kernel-Level Syscall Filtering (seccomp) (medium)
CVSS (Common Vulnerability Scoring System) のスコアの詳細
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).
以下の CSVV メトリクスおよびスコアは予備的で、再検討の対象となります。
CVSS v3 スコアの内訳
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| ベーススコア | 9.6 | N/A | 9.6 |
| 攻撃ベクトル | Network | N/A | Network |
| 攻撃の複雑さ | Low | N/A | Low |
| 必要な権限 | None | N/A | None |
| ユーザー関与レベル | Required | N/A | Required |
| 範囲 | Changed | N/A | Changed |
| 機密性 | High | N/A | High |
| 完全性への影響 | High | N/A | High |
| 可用性への影響 | High | N/A | High |
ベクトル
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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
脆弱性の原因 (CWE) の理解
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands; Modify Memory
This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. If the memory accessible by the attacker can be effectively controlled, it may be possible to execute arbitrary code, as with a standard buffer overflow. If the attacker can overwrite a pointer's worth of memory (usually 32 or 64 bits), they can alter the intended control flow by redirecting a function pointer to their own malicious code. Even when the attacker can only modify a single byte, arbitrary code execution can be possible. Sometimes this is because the same problem can be exploited repeatedly to the same effect. Other times it is because the attacker can overwrite security-critical application-specific data -- such as a flag indicating whether the user is an administrator.
Availability,Confidentiality
Technical Impact: Read Memory; DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory)
Out of bounds memory access will very likely result in the corruption of relevant memory, and perhaps instructions, possibly leading to a crash. Other attacks leading to lack of availability are possible, including putting the program into an infinite loop.
Confidentiality
Technical Impact: Read Memory
In the case of an out-of-bounds read, the attacker may have access to sensitive information. If the sensitive information contains system details, such as the current buffer's position in memory, this knowledge can be used to craft further attacks, possibly with more severe consequences.
よくある質問
Not sure what something means? Check out our Security Glossary.
エラータ通知の受信を希望しますか? こちらで登録してください。
