EUVD-2026-39045
GHSA-f88h-fjvm-fgph
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Network-reachable via a crafted page needing only a page visit (UI:R) and no auth (PR:N); use-after-free yields full renderer-process compromise, but scope stays Unchanged as code runs inside the sandbox.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Use after free in Blink in Google Chrome prior to 149.0.7827.197 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Remote code execution in Google Chrome's Blink rendering engine (versions prior to 149.0.7827.197) allows a remote attacker to run arbitrary code within the renderer sandbox when a victim visits a crafted HTML page. The flaw is a use-after-free (CWE-416) rated High by Chromium with a CVSS 8.8; no public exploit identified at time of analysis and it is not listed in CISA KEV, though Chrome browser bugs of this class are historically high-value targets. …
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 the victim to load attacker-controlled HTML content in an unpatched Chrome (before 149.0.7827.197) - this is the explicit user-interaction prerequisite encoded as UI:R in the CVSS vector, satisfiable by visiting a malicious site, a compromised legitimate site, or rendering attacker content in an iframe/ad. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals are partly conflicting and should be weighed carefully. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker hosts a crafted HTML page (or injects it via a compromised ad network or watering-hole site) that drives Blink into freeing and then re-referencing a DOM-related object. A victim running an unpatched Chrome simply visits the page (UI:R), triggering the use-after-free and granting the attacker arbitrary code execution inside the renderer sandbox - typically the first stage of a chain that would pair with a separate sandbox escape for full host compromise. … |
| Remediation | Vendor-released patch: Google Chrome 149.0.7827.197 (Stable channel) - update to this version or later via Chrome's built-in updater (chrome://settings/help) and relaunch to apply, then confirm Chromium-derived browsers (Edge, Brave, Opera, Vivaldi) pick up the corresponding Blink fix from their own vendors. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Issue mandatory update notification requiring Chrome 149.0.7827.197 or later and deploy endpoint policies to block legacy versions. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-416 – Use After Free
View allSame technique Memory Corruption
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today