Google Chrome: Memory corruption in Omnibox
Summary
Memory corruption in the Omnibox (address bar and search box) of Google Chrome allows a remote attacker to potentially execute arbitrary code inside the browser sandbox. The attack requires that a victim opens a crafted HTML page. Full compromise of the system would normally require an additional sandbox escape.
Affected
- Google Chrome (desktop) prior to 156.0.8078.47
Fixed in
- Google Chrome 156.0.8078.47 and later (Linux, per secondary coverage)
- Google Chrome 156.0.8078.47 or 156.0.8078.48 (Windows and macOS, per secondary coverage; verify against the vendor advisory)
- Google Chrome for Android 156.0.8078.47, rolled out via Google Play over several days
- Microsoft Edge 156.0.4314.42 or later (per government CERT bulletin)
- Ubuntu: chromium-browser is not affected because it installs the Chromium snap; update the snap channel
Workaround
Unknown. No workaround is documented in the sources. The fix is the browser update.
Exploitation
- No evidence of active exploitation found.
- No public proof of concept found; this does not prove that none exists.
- One third-party tracker lists the CVE as not in the CISA KEV catalogue; not checked directly.
Our recommendation
- Update Google Chrome to 156.0.8078.47 or later on all desktops and Android devices, and restart the browser so the update takes effect.
- Update Microsoft Edge and snap-based Chromium to the fixed versions.
- Use Chrome Browser Cloud Management or a similar tool to find devices below the fixed build.
- Verify the build numbers against the Chrome Releases post before rollout, and recheck the KEV status and PoC availability before closing the ticket.
- Apply the update in the normal browser patch cycle, with faster rollout for internet-facing or high-risk users.
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 entry issues.chromium.org
- Ubuntu CVE tracker ubuntu.com
- Hong Kong CERT: Microsoft Edge multiple vulnerabilities www.hkcert.org
- Vulners CVE record CVE-2026-113176 vulners.com
- Cyberexperts: Chrome 156 update cyberexperts.com
- Dijitalturk: Chrome 156 update patches 353 security vulnerabilities dijitalturk.com
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, 13:16.
Original description (NVD)
Memory corruption in Omnibox 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: Medium)
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.