CVE-2026-6300 is a high-severity use-after-free vulnerability in the Blink CSS layout engine in Google Chrome prior to 147.0.7727.101. The flaw is rooted in Blink's LocalFrameView::PerformLayout() logic, where layout processing iterates over a list of layout subtree roots while interleaved style recalculation can mutate that same list. Under crafted HTML and CSS conditions, including layout changes driven by container-query-related style recalculation, an element can transition to a state such as display:none and its associated LayoutObject can be destroyed while still being referenced by the active iteration. This leaves a dangling pointer that can later be dereferenced, producing a use-after-free condition. A remote attacker can trigger the bug by causing a target to load a crafted web page, leading to arbitrary code execution within Chrome's renderer sandbox.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a small browser exploit proof-of-concept consisting of three files: an HTML page, a JavaScript exploit scaffold, and a CSS file. The overall purpose is to demonstrate a browser-engine memory corruption scenario tied to CSS container queries and DOM layout invalidation. In poc.html, a container-query rule hides #vulnerable_element when the container width drops below 400px. The script logic in pwn.js forces layout on the target element, shrinks the container from 500px to 300px, and forces another layout flush, matching the comment that the target element's LayoutObject may be freed mid-iteration. After the suspected corruption trigger, the code performs heap grooming by allocating 2000 div elements with a size-controlled attribute payload to reclaim freed memory with attacker-influenced contents. It then requests pointer lock and creates typed-array/DataView objects wrapped by SandboxMemoryManager, which exposes read64 and write64 methods intended as arbitrary memory access primitives once object corruption is achieved. The repository does not include a full exploit chain, sandbox escape, or RCE payload, and there are no network callbacks or external C2 endpoints. One notable inconsistency is that poc.html loads exploit.js, but the repository contains pwn.js; this suggests the PoC is incomplete or the script filename was changed without updating the HTML. Overall, this is a browser-side memory corruption PoC scaffold rather than a weaponized exploit.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A use-after-free vulnerability in the CSS component of Google Chrome that allows remote code execution inside the sandbox via a crafted HTML page.
A high-severity use-after-free vulnerability in CSS in Google Chrome.
A high-severity use-after-free remote code execution vulnerability in Google Chrome's Blink CSS/layout engine that can be triggered by a crafted HTML page during interleaved style recalculation in layout processing.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.