Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Race condition in Google Chrome DevTools

IdentifiersCVE-2026-2319CWE-362· Concurrent Execution using Shared…

CVE-2026-2319 is a medium-severity race condition in the DevTools component of Google Chrome affecting versions prior to 145.0.7632.45. According to the provided description, a remote attacker may be able to trigger object corruption by using a malicious file, but exploitation requires the victim to perform specific UI gestures and install a malicious browser extension. The issue is therefore not a simple drive-by bug; it depends on a narrow set of attacker-controlled timing and user-assisted conditions in DevTools-related processing that can lead to memory/object state corruption.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause object corruption in Chrome DevTools. Based on the provided material, this may enable further exploitation depending on attacker control of the malicious file and the required interaction sequence. The supporting content characterizes the likely outcomes of the broader Chrome update set as including browser manipulation or security bypass, but for this specific CVE the confirmed impact in the provided data is object corruption with potential for follow-on exploitation.

Mitigation

If you can’t patch tonight, do this now.

Until patching is completed, reduce exposure by preventing installation of untrusted Chrome extensions, using enterprise extension allowlisting/blocklisting where available, limiting user access to untrusted or attacker-supplied files, and reducing opportunities for social engineering that could induce the required UI gestures. Restricting DevTools use and extension installation on high-risk systems may further reduce exploitability.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 145.0.7632.45 or later. For Windows and macOS, Google recommends updating to 145.0.7632.45/46; for Linux, update to 145.0.7632.45. If using downstream Chromium packages, apply the vendor-provided fixed package versions for the relevant distribution.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleChromeapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity5

Community discussion across Reddit, Mastodon, and other social sources.

Race condition in Google Chrome DevTools (CVE-2026-2319) | Mallory