Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Race condition demands precise timing (AC:H); victim must visit crafted page (UI:R); process memory leakage justifies C:H; no write or availability impact observed.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
6DescriptionNVD
Race in WebCodecs in Google Chrome prior to 147.0.7727.55 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Race condition in Chrome's WebCodecs component allows a remote attacker to read sensitive data from process memory by luring a victim to a crafted HTML page. Affected versions are all Google Chrome releases prior to 147.0.7727.55. No public exploit code or active exploitation has been identified; EPSS sits at 0.03% (8th percentile), reflecting very low real-world exploitation probability despite the high confidentiality impact rating.
Technical ContextAI
WebCodecs is a low-level browser API introduced in Chrome 94 that exposes audio and video codec primitives directly to JavaScript, enabling high-performance media processing pipelines. CWE-362 (Concurrent Execution Using Shared Resource with Improper Synchronization) indicates the WebCodecs implementation contains a race condition - likely a time-of-check/time-of-use (TOCTOU) flaw - where concurrent operations on a shared memory buffer or codec state object are not properly serialized. A crafted HTML page can manipulate codec operations to open a narrow window during which out-of-scope process memory becomes readable by the renderer. The affected CPE is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* covering all Chrome desktop versions below 147.0.7727.55.
RemediationAI
Update Google Chrome to version 147.0.7727.55 or later using Chrome's built-in updater (chrome://settings/help) or via enterprise deployment channels, as announced at http://chromereleases.googleblog.com/2026/04/stable-channel-update-for-desktop.html. For environments where immediate patching is not feasible, consider restricting navigation to untrusted or external websites via enterprise policy - note this has significant usability trade-offs. Chrome's Site Isolation feature (enabled by default) partially limits cross-site memory exposure but does not fully mitigate intra-process race conditions within the renderer. Disabling the WebCodecs API via enterprise policy (BlockThirdPartyCookies or renderer-side feature flags) may eliminate the attack surface but will break legitimate media-heavy web applications. Patch deployment is strongly preferred over compensating controls given the complexity of reliable exploitation.
Same weakness CWE-362 – Race Condition
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Medium| Product | Status |
|---|---|
| SUSE Package Hub 15 SP6 | Fixed |
| openSUSE Leap 15.6 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP6 | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-20707
GHSA-2fw9-cxch-qx5h