CVE-2024-6778 is a high-severity race condition in Chrome DevTools affecting Google Chrome versions prior to 126.0.6478.182. A crafted malicious Chrome extension can exploit the race to inject script or HTML content into a privileged Chrome page.
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 (2 hidden).
This repository provides proof-of-concept (POC) exploits for CVE-2024-5836 and CVE-2024-6778, both affecting the Chromium browser (including Chrome) prior to version 126.0.6478.54. The repository is organized into three main directories: 'CVE-2024-5836', 'CVE-2024-6778', and 'sandbox-escape'. Each directory contains a Chrome extension (manifest, devtools page, worker, and supporting files) that demonstrates exploitation of the respective vulnerability. - The 'CVE-2024-5836' and 'CVE-2024-6778' directories each contain a POC extension that abuses a race condition or permissions bypass in the Chrome DevTools API to inject arbitrary JavaScript into privileged WebUI pages (e.g., chrome://settings). - The 'sandbox-escape' directory contains a full exploit chain leveraging CVE-2024-6778 to gain code execution in the 'chrome://policy' page. The exploit sets malicious Chrome policies (such as 'AlternativeBrowserPath' and 'AlternativeBrowserParameters') to trigger the BrowserSwitcher feature, causing Chrome to launch a system executable (e.g., cmd.exe, bash, or Calculator) with attacker-controlled arguments. This results in a sandbox escape and arbitrary code execution on the host system. The exploit is operational and demonstrates a real-world attack chain from extension context to host code execution. The repository is well-structured, with each exploit as a standalone Chrome extension, and includes a README with detailed context and references. The main attack vector is via a malicious browser extension, and the exploit targets privileged Chrome WebUI endpoints and system executables as part of the payload.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.