EUVD-2026-35245
GHSA-x2hh-w9mw-3vq2
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Primary rating from NVD.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
5DescriptionCVE.org
Out of bounds read and write in V8 in Google Chrome prior to 149.0.7827.103 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Articles & Coverage 1
AnalysisAI
Remote code execution in Google Chrome's V8 JavaScript engine prior to 149.0.7827.103 allows a remote attacker to execute arbitrary code inside the renderer sandbox by enticing a victim to visit a crafted HTML page. The flaw is an out-of-bounds read and write (CWE-125) rated High severity by Chromium with a CVSS 8.8, and no public exploit identified at time of analysis, though V8 memory-corruption issues historically attract exploit development.
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 | Victim must use Google Chrome at a version prior to 149.0.7827.103 and load attacker-controlled HTML/JavaScript in the browser (UI:R - user interaction required, typically a single page visit). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals point to a real but conditional risk: the CVSS 8.8 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) confirms network-reachable, unauthenticated exploitation requiring user interaction (visiting a page), with scope unchanged because code execution remains inside the sandboxed renderer. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker hosts or compromises a website containing crafted JavaScript that triggers the V8 out-of-bounds read/write; a user browsing with a vulnerable Chrome build visits the page (e.g., via phishing link, malvertising, or watering-hole) and the script gains arbitrary code execution inside the renderer sandbox. Without a separate sandbox escape the attacker is limited to renderer-level capabilities such as cross-origin data theft, credential exfiltration from in-process secrets, and staging further exploits; no public POC is identified at time of analysis. |
| Remediation | Vendor-released patch: Chrome 149.0.7827.103 or later on the Stable channel - update immediately via Chrome's built-in updater or by deploying the latest MSI/PKG/DEB package, and restart the browser to activate the fix as described in the Chrome Releases advisory (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0153744567.html) and tracking issue https://issues.chromium.org/issues/506689381. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
24 hours: Identify Chrome deployment scope and inventory across endpoints. …
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