EUVD-2026-35220
GHSA-qhww-xqqg-m6hv
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Primary rating from NVD.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Use after free in ServiceWorker in Google Chrome prior to 149.0.7827.103 allowed a remote attacker who had compromised the renderer process to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Sandboxed remote code execution in Google Chrome versions prior to 149.0.7827.103 allows attackers who have already compromised the renderer process to execute arbitrary code via a crafted HTML page that triggers a use-after-free in the ServiceWorker component. Rated High severity by Chromium with a CVSS 7.5, the flaw requires user interaction (visiting a malicious page) and a pre-existing renderer compromise, and no public exploit has been identified at time of analysis. …
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 | The attacker must have already compromised the Chrome renderer process (typically via a separate renderer bug) before this flaw can be triggered, and the victim must interact by loading a crafted HTML page that registers/manipulates a malicious ServiceWorker. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H) scores 7.5 (High), reflecting network reach but tempered by High attack complexity and required user interaction. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first achieves code execution in a Chrome renderer process via a separate vulnerability (for example a V8 type-confusion bug) on a victim who visits an attacker-controlled site. From that foothold, attacker-supplied JavaScript on the crafted HTML page registers and manipulates a ServiceWorker to trigger the use-after-free, gaining a stable memory-corruption primitive used to execute arbitrary code still inside the renderer sandbox - a typical stepping stone toward a follow-on sandbox-escape exploit. … |
| Remediation | Update Google Chrome to 149.0.7827.103 or later via the Stable channel; the patch is available per the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0153744567.html and tracked in the upstream issue https://issues.chromium.org/issues/517705966. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Deploy Chrome version 149.0.7827.103 or later organization-wide; enable auto-update enforcement if not already active; issue mandatory user notification. …
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