CVE-2026-113173
Description
A flaw was found in Google Chrome. This vulnerability allows a remote attacker to execute arbitrary code within the sandbox (an isolated security environment) by convincing a user to visit a crafted HTML page. The issue is caused by improper input validation in the user interface (UI) component.
Statement
Red Hat has rated this vulnerability as having Important severity because an unauthenticated remote attacker could execute arbitrary instructions within the confined sandbox environment if a local user opens a specially crafted website. Although triggering the flaw requires social engineering or user interaction, the resulting code execution within the browser process elevates the risk to Important rather than Moderate. Chromium is not included in supported Red Hat Enterprise Linux repositories and is distributed only through community channels such as EPEL.
Understanding the Weakness (CWE)
Access Control
Technical Impact: Bypass Protection Mechanism
In some cases, injectable code controls authentication; this may lead to a remote vulnerability.
Access Control
Technical Impact: Gain Privileges or Assume Identity
Injected code can access resources that the attacker is directly prevented from accessing.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
When a product allows a user's input to contain code syntax, it might be possible for an attacker to craft the code in such a way that it will alter the intended control flow of the product. As a result, code injection can often result in the execution of arbitrary code. Code injection attacks can also lead to loss of data integrity in nearly all cases, since the control-plane data injected is always incidental to data recall or writing.
Non-Repudiation
Technical Impact: Hide Activities
Often the actions performed by injected control code are unlogged.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
