CVE-2026-121233
Description
A type confusion flaw was found in the CacheStorage 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 validate indirect call targets and object types using Control Flow Integrity to prevent execution hijacking in Chromium's CacheStorage component: upgrade to Chromium 157.0.8103.38 (or the fixed Chromium builds), which resolves the type confusion flaw in the CacheStorage component when handling browser cache objects, closing crafted HTML page. Until patched, this is a concern on Chromium browser deployments on any platform, so Prevent users from accessing untrusted or unverified web pages and maintain renderer process sandboxing to contain arbitrary execution inside the sandbox boundary. As a compensating measure, Restrict V8 JIT compilation and isolate the renderer heap via sandboxing to constrain exploitation of CacheStorage type confusion, Enable Address Space Layout Randomization across browser processes to require memory leaks before redirecting control flow, and Enforce non-executable memory permissions on heap and data pages to block direct shellcode execution. These controls limit blast radius and contain exploitation, but they do not fix the underlying type confusion defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-113 Control Flow Integrity (CFI / Shadow Call Stack) (high)
Understanding the Weakness (CWE)
Other
Technical Impact: Varies by Context
When the product accesses the resource using an incompatible type, this could trigger logical errors because the resource does not have expected properties.
Availability,Integrity,Confidentiality
Technical Impact: Read Memory; Modify Memory; Execute Unauthorized Code or Commands; DoS: Crash, Exit, or Restart
If a memory buffer is accessed using an incompatible type, and the allocated buffer is smaller than the type that the code is attempting to access, then an attacker could read or write memory outside the bounds of the buffer, leading to a crash or possibly code execution.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
