CVE-2026-121112
Description
An out of bounds read flaw was found in the Permissions 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 sanitize and bounds-check IPC messages received by the Permissions component from the renderer process to prevent sandbox escape: upgrade to Google Chrome 157.0.8103.38 (or the fixed Chromium builds), which prevents an out-of-bounds read in the Chromium Permissions component when processing input from the renderer process, closing all 2 injection vectors (crafted HTML page, compromised renderer IPC message). Until patched, this is a concern on all platforms running Chromium or Google Chrome desktop browsers, so restrict untrusted web browsing and isolate browser sessions to reduce the risk of renderer compromise and subsequent sandbox escape. As a compensating measure, ASLR to randomize address space layout, hindering the attacker's ability to locate code or data structures via memory reads, NX/XD bit to block execution of shellcode in writable memory pages if arbitrary code execution is attempted, EDR agent to detect post-exploitation behavior and anomalous processes spawned outside the browser sandbox, Falco / eBPF runtime security to monitor and detect unexpected process spawning or suspicious file access from the browser, Full RELRO and PIE to enforce read-only GOT and full position-independent execution, hardening the binary against memory corruption, and Control Flow Integrity (CFI / Shadow Call Stack) to restrict unauthorized control-flow transfers such as ROP or JOP chains. These controls limit blast radius and contain exploitation, but they do not fix the underlying out-of-bounds read defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-101 ASLR (Address Space Layout Randomization) (medium)
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.
Confidentiality
Technical Impact: Bypass Protection Mechanism
Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.
Other
Technical Impact: Varies by Context
The read operation could produce other 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.
