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

Sandbox escape in Google Chrome DevTools

IdentifiersCVE-2026-13025CWE-20

CVE-2026-13025 is a high-severity race condition / insufficient validation of untrusted input vulnerability in DevTools in Google Chrome prior to 149.0.7827.197. According to the provided advisory, a remote attacker who had already compromised the renderer process could trigger the issue via a crafted HTML page and potentially escape Chrome’s sandbox. The available source material characterizes the flaw as affecting DevTools and involving insufficient input validation, but does not provide vulnerable function-level details.

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.

Start free trial
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 could allow an attacker who already achieved renderer-process compromise to break out of the browser sandbox. This would bypass a key Chrome security boundary and could enable code execution or other malicious actions outside the renderer sandbox, increasing the likelihood of broader system compromise.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting use of untrusted websites and untrusted HTML content until the browser is updated. Because exploitation requires prior renderer compromise, minimizing exposure to renderer-compromise vectors and applying Chrome updates promptly are the primary mitigations. No specific vendor workaround beyond updating was provided in the supplied content.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 149.0.7827.197 or later. The fixed Stable channel versions referenced in the provided content are 149.0.7827.196/197 for Windows and Mac and 149.0.7827.196 for Linux; the advisory specifically states 149.0.7827.197 or later as the remediation for this CVE.
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.

ACTIVITY FEED

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

4 SOURCESView more in app
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.
Start free trial
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 activity1

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

EXTERNAL REFERENCES
MITRE CVE
cve.org · CVE-2026-13025
NVD
nvd.nist.gov/vuln/detail/CVE-2026-13025
MITRE CWE · CWE-20
cwe.mitre.org