Google Chrome: Memory corruption in DisplayLocking
Summary
Google Chrome contains a memory corruption flaw in the DisplayLocking component (CWE-119). A remote attacker who lures a user to a crafted HTML page could potentially execute arbitrary code inside the browser sandbox. The attack requires user interaction, such as visiting the page, but no login or privileges. Google rates the Chromium severity as High and the CVSS 3.1 base score is 8.8.
Affected
- Google Chrome before 156.0.8078.47, according to the CVE record.
- Third-party reports indicate that Windows and macOS builds before 156.0.8078.48 are affected and that Android builds before 156.0.8078.47 are affected. Not confirmed by Google.
- Chromium-based browsers that ingest the fix, such as Microsoft Edge, may also be affected until they are updated.
Fixed in
- Google Chrome 156.0.8078.47 for Linux, according to third-party reports.
- Google Chrome 156.0.8078.47 or 156.0.8078.48 for Windows and macOS, according to third-party reports.
- Verify the exact fixed build against Google's Chrome Releases post. Later stable builds exist and should be preferred.
Workaround
- Unknown. No vendor workaround has been identified. Update the browser.
- Restart the browser after updating, because the update takes effect only after a relaunch.
Exploitation
- No evidence of in-the-wild exploitation was found in the sources reviewed. The Strix record lists KEV: No; the CISA KEV catalog was not checked directly.
- No public proof of concept was found.
- VulDB reports an estimated exploit market price of USD 5,000 to 25,000. This is a market estimate, not evidence of exploitation.
Our recommendation
- Update Google Chrome on all endpoints to the current stable build, and deploy within days.
- Also update Microsoft Edge and other Chromium-based browsers.
- Verify the installed version on all endpoints and confirm that the browser was restarted after the update.
- Monitor for reports of exploitation and for further Chrome security updates.
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 bug tracker 567612004 issues.chromium.org
- Microsoft Security Update Guide: CVE-2026-113093 msrc.microsoft.com
- VulDB: CVE-2026-113093 vuldb.com
- Strix: CVE-2026-113093 www.strix.ai
- Vulners: CVELIST CVE-2026-113093 vulners.com
- Ubuntu Security: CVE-2026-113093 ubuntu.com
- Cybersecurity News: Chrome security update fixing 353 flaws cybersecuritynews.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, 14:04.
Original description (NVD)
Memory corruption in DisplayLocking 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: High)
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.