CVE-2026-113202
Description
A flaw was found in the BrowserTag component of chromium-browser. A remote attacker could exploit this vulnerability to execute arbitrary code within the browser sandbox by convincing a user to open a specially crafted HTML page. This issue is caused by a use-after-free condition, where the application attempts to access memory that has already been released.
Statement
Red Hat Product Security rates this vulnerability as having an Important impact because successful exploitation permits code execution within the browser sandbox without authentication. Although triggering the condition requires social engineering to trick a user into visiting a malicious HTML page, it directly threatens the confidentiality and integrity of the renderer process. Furthermore, Chromium is not shipped in core Red Hat Enterprise Linux releases and is maintained only in community repositories such as EPEL and Fedora.
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
