CVE-2026-118327
개요
A memory corruption flaw was found in the Media 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-03) ---
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 enforce Control Flow Integrity and strict renderer process sandboxing to prevent control-flow hijacking within Chromium's Media component: upgrade to Google Chrome 156.0.8078.73 (or the fixed Chromium builds), which resolves memory corruption in the Media component during media processing, closing crafted HTML page. Until patched, this is a concern on Chromium browser users navigating to untrusted or malicious web pages, so Restrict web browsing to trusted sites and avoid opening untrusted or unverified HTML links. As a compensating measure, Enable ASLR to randomize the Chromium process address space and prevent predictable memory exploitation, Enforce NX/XD non-executable memory permissions on stack and heap pages to block shellcode execution in corrupted media buffers, Ensure Full RELRO and PIE are enabled to protect relocation tables and prevent code reuse attacks, Utilize kernel-level seccomp syscall filtering to contain the renderer process from unauthorized kernel interactions, and Deploy an EDR agent to monitor and alert on anomalous memory exploitation activity from the browser process. 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-113 Control Flow Integrity (CFI / Shadow Call Stack) (high)
취약점 이해 (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.
