Google Chrome: Memory corruption in BrowserTag allows code execution in sandbox
Summary
Google Chrome contains a memory corruption flaw in its BrowserTag component (CWE-119). A remote attacker can create a crafted HTML page that may execute arbitrary code inside the browser sandbox if a user opens it. Exploitation requires user interaction, such as visiting a malicious link. Chromium rates the issue Low, and no exploitation has been reported.
Affected
- Google Chrome (desktop) prior to 156.0.8078.47
Fixed in
- Google Chrome 156.0.8078.47 or later, according to the CVE description. The exact build containing this fix is not confirmed in the vendor text available to us.
- Newer Stable builds have been released; install the latest version.
- Chromium-based distributions (Debian, Chainguard) and Microsoft Edge ship their own fixed versions; check their advisories.
Workaround
- No workaround known. Updating Chrome is the only remedy.
Exploitation
- Chromium rates the issue Low.
- CISA SSVC: exploitation none, not automatable, total technical impact.
- No reports of exploitation in the wild or public proof-of-concept code were found. The CISA KEV catalogue was not checked.
Our recommendation
- Update Chrome to the latest Stable version on all endpoints.
- Enforce a minimum Chrome version through your endpoint management tool and verify that automatic updates are not disabled.
- Ask users to restart the browser after an update and confirm the version under Help > About Google Chrome.
- Check Chromium-based browsers (Edge, Brave, Opera) for their own updates.
- Monitor for exploitation reports, as this CVE was published recently.
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- Chrome Releases: Stable Channel Update for Desktop chromereleases.googleblog.com
- Chromium issue tracker issues.chromium.org
- CVE record aggregator (Vulners) vulners.com
- Chainguard/OSV advisory osv.dev
- Ubuntu security notice ubuntu.com
- Microsoft Edge advisory via HKCERT www.hkcert.org
Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 31 Oct 2026, 12:30.
Original description (NVD)
Memory corruption in BrowserTag in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Low)
Sources
The tracker combines official, freely usable data sources – updated continuously:
- NVD (NIST) – CVEs, rating (CVSS), affected products
- CISA KEV – vulnerabilities confirmed by CISA as actively exploited
- CISA Vulnrichment – CISA assessment (SSVC) in the official CVE record
- FIRST EPSS – probability of exploitation
- Microsoft MSRC – Patch Tuesday: vulnerabilities, severity, updates
- PoC-in-GitHub – public proof-of-concept repositories
- Metasploit (Rapid7) – modules of the Metasploit Framework
- Exploit-DB (OffSec) – archive of public exploits (links only)
- Patch days: official vendor pages (linked per vendor) (Vendor patch days)
This product uses data from the NVD API but is not endorsed or certified by the NVD. EPSS data © FIRST.org.
Affected? We can help.
We check whether your systems are affected, install updates and close the gap – continuously with the System Health Checker if you wish.