Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Network delivery via crafted HTML requires only user navigation (UI:R, PR:N); impact is confidentiality-only memory read with no integrity or availability effect.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionCVE.org
Type Confusion in V8 in Google Chrome prior to 148.0.7778.168 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Type confusion in V8, Chrome's JavaScript engine, exposes potentially sensitive process memory to remote attackers in all Chrome versions prior to 148.0.7778.168. Exploitation requires a victim to navigate to a specially crafted HTML page, after which the type confusion bug can be leveraged to read memory contents from the renderer process. No active exploitation is confirmed (not in CISA KEV), EPSS is extremely low at 0.03%, and SSVC classifies exploitation as none - placing real-world urgency in the routine patching tier despite the CVSS 6.5 rating.
Technical ContextAI
V8 is the open-source JavaScript and WebAssembly engine embedded in Google Chrome and Chromium-based browsers. CWE-843 (Type Confusion) occurs when an object or resource is accessed using a type incompatible with how it was originally allocated - in a JIT-compiled engine like V8, this can cause the engine to misinterpret memory regions, permitting reads of adjacent or otherwise inaccessible memory. The affected CPE is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* covering all Chrome versions before 148.0.7778.168 across platforms, consistent with the tags referencing Google, Red Hat, and SUSE distributions that package Chromium. The Chromium security team classified this as Medium severity, aligning with the confidentiality-only impact profile.
RemediationAI
The primary fix is to update Google Chrome to version 148.0.7778.168 or later, as confirmed by the vendor's stable channel advisory at https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_12.html. Chrome's automatic update mechanism will deploy this for most desktop users without manual intervention; administrators managing enterprise fleets should push the update via policy. For Red Hat and SUSE environments distributing Chromium packages, monitor distribution-specific security advisories for downstream patch availability. If immediate patching is not possible, disabling JavaScript execution via enterprise policy (e.g., Chrome's DefaultJavaScriptSetting policy) eliminates the V8 attack surface entirely but will break most modern web functionality and should be considered only as a short-term measure in high-risk environments. No other confirmed workarounds are available for this specific V8 type confusion issue.
Same technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Medium| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-30385
GHSA-2863-2m4q-93pg