CVE-2026-118335
Description
An improper input validation flaw was found in the Metrics 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-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 strict allowlist input validation on inputs passed to the Chromium Metrics subsystem to prevent code execution inside the sandbox: upgrade to Google Chrome 156.0.8078.73 (or the fixed Chromium builds), which validates input in the Metrics component to prevent processing malformed input delivered via web content, closing crafted HTML page. Until patched, this is only a concern on macOS workstations running Chromium or Google Chrome — Non-macOS platforms such as Linux and Windows are unaffected — so Restrict users from navigating to untrusted or external websites and filter access through secure web gateways. As a compensating measure, Deploy an EDR agent to detect anomalous post-exploitation behavior and unauthorized payload execution inside the browser sandbox on macOS. These controls limit blast radius and contain exploitation, but they do not fix the underlying improper input validation defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-1315 Allowlist-Preferred Input Validation (Deny-by-Default Filtering) (high)
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory)
An attacker could provide unexpected values and cause a program crash or arbitrary control of resource allocation, leading to excessive consumption of resources such as memory and CPU.
Confidentiality
Technical Impact: Read Memory; Read Files or Directories
An attacker could read confidential data if they are able to control resource references.
Integrity,Confidentiality,Availability
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
An attacker could use malicious input to modify data or possibly alter control flow in unexpected ways, including arbitrary command execution.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
