EUVD-2026-40597
GHSA-2w8q-jwxq-9mrg
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
AC:H captures the mandatory renderer-compromise prerequisite; C:H reflects direct process memory read; no integrity or availability impact exists.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Insufficient policy enforcement in Spellcheck in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Insufficient policy enforcement in the Spellcheck component of Google Chrome prior to 150.0.7871.47 exposes process memory to attackers who have already achieved renderer process compromise. The vulnerability enables a second-stage information disclosure step in a chained attack: after compromising the renderer, the attacker serves a crafted HTML page that exploits the Spellcheck policy gap to read potentially sensitive data from memory. No public exploit code or active exploitation via CISA KEV has been identified at time of analysis; Google has released a fix in the stable channel update.
Technical ContextAI
Google Chrome's renderer process executes untrusted web content in a sandboxed environment, with inter-process policies restricting what renderer code can access. CWE-20 (Improper Input Validation) indicates the Spellcheck subsystem fails to adequately validate or enforce policy boundaries on data it handles within the renderer context. When the renderer process has been compromised - typically via a separate memory-corruption or type-confusion vulnerability - this policy enforcement gap allows the compromised renderer to surface memory contents that should be inaccessible. The affected version range is Chrome prior to 150.0.7871.47, as identified by EUVD-2026-40597 and the Chrome stable channel advisory. CPE-level specificity is limited to the Chrome browser binary; no separate library or component CPE is published for the Spellcheck subsystem.
RemediationAI
Update Google Chrome to version 150.0.7871.47 or later, which includes the Spellcheck policy enforcement fix per the vendor stable channel advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. Chrome's auto-update mechanism will deliver this patch automatically in most managed and consumer deployments; administrators should verify that fleet devices have applied the update via policy dashboards or endpoint management tools. Because this vulnerability requires a compromised renderer as a prerequisite, organizations should also audit Chrome version compliance for all other currently disclosed renderer-targeting CVEs - eliminating the renderer compromise vector removes the exploitation path for this flaw entirely. No specific workaround exists for the Spellcheck policy gap itself short of applying the patch; disabling Spellcheck via enterprise policy (SpellcheckEnabled=false) would remove the vulnerable surface but carries usability trade-offs for end users and is not officially recommended by Google as a mitigation for this CVE.
Same weakness CWE-20 – Improper Input Validation
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today