Severity by source
AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Sandbox escape constitutes a scope change (S:C); otherwise AV:A and AC:H reflect adjacent-only, race-condition timing constraints with no auth or interaction required.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Lifecycle Timeline
3DescriptionCVE.org
Race condition in Enterprise in Google Chrome on on Windows prior to 152.0.7977.65 allowed an adjacent attacker to potentially execute arbitrary code outside the sandbox via crafted network traffic. (Chromium security severity: Low)
AnalysisAI
Race condition in Google Chrome Enterprise on Windows prior to version 152.0.7977.65 enables an adjacent network attacker to potentially escape the browser sandbox and execute arbitrary code on the host system via crafted network traffic. No public exploit code has been identified and CISA has not listed this in the Known Exploited Vulnerabilities catalog. …
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 be network-adjacent (same LAN, WLAN, or equivalent Layer-2/3 segment) - remote internet-based exploitation is not possible given AV:A. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector (AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) yields a base score of 7.5 but contains several moderating factors: AV:A restricts exploitation to the adjacent network segment (LAN, WLAN, or Bluetooth range), and AC:H reflects the race condition's inherent timing sensitivity, requiring precise exploitation windows that resist reliable automation. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker positioned on the same local network segment - such as a co-located user on a corporate WLAN or an attacker who has already compromised another LAN host - sends specially crafted network traffic to a Windows machine running Chrome Enterprise. The traffic is timed to exploit a race condition in Chrome's network processing code, hitting a narrow timing window that allows execution of attacker-controlled code in a context outside Chrome's sandbox. … |
| Remediation | The primary fix is upgrading Chrome Enterprise on Windows to version 152.0.7977.65 or later, as confirmed by Google's stable channel update advisory at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, identify all Windows Chrome Enterprise installations running versions prior to 152.0.7977.65 and assess update availability in your environment. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-362 – Race Condition
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-66084
GHSA-7c7x-vf6q-h3xx