CVE-2026-118347
Description
An use after free flaw was found in the FileSystem 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 ensure safe object lifecycle management and eliminate dangling pointer dereferences in the Chromium FileSystem component: upgrade to Google Chrome 156.0.8078.73+ (or the fixed Chromium builds), which corrects memory reclamation and object lifetime handling in the FileSystem component to prevent use-after-free conditions, closing crafted HTML page interacting with the FileSystem API. Until patched, this is a concern on Chromium and Google Chrome desktop and browser deployments across all operating systems, so restrict user navigation to trusted sites and prevent users from opening untrusted or attacker-controlled HTML pages. As a compensating measure, Maintain Address Space Layout Randomization to hinder payload and gadget redirection following heap corruption, Enforce Non-Executable Memory (NX/XD bit) to block shellcode execution within freed heap memory regions, Enable full RELRO and PIE to make the Global Offset Table read-only and randomize executable base addresses, and Apply Control Flow Integrity and Shadow Call Stack to validate indirect call targets against control-flow hijacking. These controls limit blast radius and contain exploitation, but they do not fix the underlying use-after-free defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-101 ASLR (Address Space Layout Randomization) (medium)
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Memory
The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.
Confidentiality
Technical Impact: Read Memory
Read operations on freed memory can sometimes leak sensitive information instead of causing a crash
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
