EUVD-2026-35218
GHSA-78gr-622p-8fm9
Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Primary rating from NVD.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Use after free in Read Anything in Google Chrome prior to 149.0.7827.103 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Sandbox escape in Google Chrome versions prior to 149.0.7827.103 allows remote attackers who have already compromised the renderer process to break out of the sandbox via a use-after-free in the Read Anything component when processing a crafted HTML page. Google rates this Chromium-severity High, and no public exploit has been identified at time of analysis, but the CVSS 8.3 score reflects the severity of full sandbox escape leading to scoped impact beyond the renderer. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires (1) a pre-existing compromise of the Chrome renderer process - the attacker must already be executing code inside the sandbox via a separate renderer bug, as explicitly stated in the CVE description; (2) the victim must load a crafted HTML page in a vulnerable Chrome version (UI:R user interaction), specifically content that exercises the Read Anything code path; and (3) the target must be running Chrome prior to 149.0.7827.103. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 8.3 vector (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H) reflects high complexity, required user interaction (visiting a malicious page), changed scope (sandbox escape), and full CIA impact - consistent with a second-stage browser exploit. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first lands a separate renderer-process RCE (via a prior 0-day or chained N-day) when a victim visits a malicious or compromised website; once code is executing inside the sandboxed renderer, the attacker triggers the Read Anything use-after-free with a crafted HTML page to corrupt heap state and pivot out of the sandbox into a more privileged Chrome process. With sandbox escape achieved, the attacker can read arbitrary user files, install persistence, and operate with the privileges of the Chrome user. … |
| Remediation | Vendor-released patch: Google Chrome 149.0.7827.103 - update Chrome via Help > About Google Chrome and relaunch the browser, or push the update through enterprise management (Chrome Browser Cloud Management, Group Policy auto-update). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Identify all systems running Chrome versions prior to 149.0.7827.103 and assess deployment scope. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Vendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today