Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Remote crafted page (AV:N, PR:N) but requires specific user UI gestures (UI:R) and non-trivial memory grooming (AC:H); successful renderer compromise yields full C/I/A impact.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
3DescriptionCVE.org
Use after free in Tab Strip in Google Chrome prior to 149.0.7827.155 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
Articles & Coverage 2
AnalysisAI
Use-after-free in the Tab Strip component of Google Chrome before 149.0.7827.155 allows a remote attacker to trigger heap corruption when a victim visits a crafted HTML page and performs specific UI gestures, potentially leading to code execution in the renderer. Google rated it High severity and a vendor patch is available, but no public exploit identified at time of analysis and it is not listed in CISA KEV. EPSS is low at 0.30% (21st percentile), and SSVC records exploitation status as none.
Technical ContextAI
The flaw is a CWE-416 use-after-free in Chrome's Tab Strip, the browser UI component that manages open tabs and their lifecycle. Use-after-free bugs occur when a pointer to freed heap memory is reused, letting an attacker reclaim the freed allocation with controlled data and corrupt the heap; in a browser renderer this is a classic primitive for achieving control-flow hijack, though modern Chrome sandboxing and mitigations (PartitionAlloc, MiraclePtr) raise exploitation difficulty. The affected product per CPE is cpe:2.3:a:google:chrome:*, i.e. the desktop Chrome browser; the same underlying Chromium fix propagates to downstream distributions, consistent with the Red Hat and SUSE tags. The reference issues.chromium.org/issues/517069848 tracks the upstream bug (access-restricted, as is typical for Chromium security issues).
RemediationAI
Vendor-released patch: update Google Chrome to 149.0.7827.155 or later via the Stable Channel; on managed fleets ensure auto-update is enabled and force a browser relaunch so the fix takes effect, and rebuild or update any embedded/Chromium-derived components. Downstream users on Red Hat or SUSE should apply the corresponding distribution browser updates once published. There is no documented feature-level workaround for this Tab Strip use-after-free; as an interim compensating control, reduce exposure by advising users not to interact with untrusted pages and, in high-security environments, deploy browsing isolation or restrict access to untrusted web content - noting this degrades usability and is not a substitute for the patch. Consult Google's advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_01750511403.html for release details.
Same weakness CWE-416 – Use After Free
View allSame technique Memory Corruption
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-37540