Google Chrome
CVE-2026-7356
HIGH
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Remote crafted page requires user navigation (UI:R) but no auth (PR:N); low-complexity UAF yielding full renderer code execution gives high C/I/A, scope unchanged.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Use after free in Navigation in Google Chrome prior to 147.0.7727.138 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Remote code execution in Google Chrome desktop builds prior to 147.0.7727.138 arises from a use-after-free in the Navigation component, letting a remote attacker who lures a victim to a crafted HTML page corrupt memory and execute arbitrary code in the renderer context. Chromium rates the flaw High severity and CVSS scores it 8.8, but there is no public exploit identified at time of analysis and EPSS is very low at 0.04% (11th percentile). A vendor patch is available and CISA's SSVC framework currently records exploitation as none.
Technical ContextAI
The defect is a CWE-416 use-after-free in Chrome's Navigation subsystem, the code path that manages document loads, session history, and navigation lifecycle inside the Blink/content layer. Use-after-free bugs occur when an object is freed while a pointer to it is still held and later dereferenced; in a browser's navigation logic these are frequently triggered by JavaScript-driven navigation, reentrancy, or object lifetime races provoked by attacker-controlled page content. Successful exploitation typically grants control over freed heap memory, enabling attacker-controlled data to be treated as a live object and steered toward code execution. The affected component is identified in CPE data as cpe:2.3:a:google:chrome (all versions prior to the fixed build), and the class of bug is the most common source of critical Chrome renderer vulnerabilities.
RemediationAI
Vendor-released patch: 147.0.7727.138 - update Google Chrome to 147.0.7727.138 or later via the Chrome Stable channel and restart the browser to apply the fix (Help > About Google Chrome forces the check), per the advisory at https://chromereleases.googleblog.com/2026/04/stable-channel-update-for-desktop_28.html. Users of Chromium-based downstream builds should apply the corresponding Red Hat or SUSE package updates once published. Because exploitation requires rendering a malicious page, interim compensating controls include restricting browsing to trusted sites and enabling enterprise policies that gate untrusted content; note these controls reduce but do not eliminate exposure and can disrupt legitimate workflows, so they are stopgaps until the patched build is deployed. No feature-level disable is available since the flaw is in core navigation, making the browser update the only complete remediation.
Same weakness CWE-416 – Use After Free
View allVendor StatusVendor
SUSE
Severity: High| Product | Status |
|---|---|
| SUSE Package Hub 15 SP6 | Fixed |
| openSUSE Leap 15.6 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| SUSE Package Hub 15 SP6 | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today