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
Out of bounds read in WebRTC in Google Chrome prior to 149.0.7827.103 allowed a remote attacker who had compromised the GPU process to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Out-of-bounds read in the WebRTC component of Google Chrome before 149.0.7827.103 enables a remote attacker who has already compromised the GPU process to escalate into heap corruption via a crafted HTML page. Google rates this High severity and a vendor patch is available; no public exploit 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 | Exploitation requires three concrete preconditions stated in or implied by the advisory: (1) the attacker must have already compromised the Chrome GPU process via a separate prior vulnerability, meaning this bug is a chain link, not an entry point; (2) the victim must load attacker-controlled HTML in Chrome (UI:R - user interaction), typically by clicking a link or visiting a malicious site; (3) the browser must be a Chrome desktop build below 149.0.7827.103 with WebRTC enabled (the default). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 7.5 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H) reflects a high-impact but high-complexity remote bug that requires user interaction (visiting a crafted page) and, per the description, a precondition that the GPU process is already compromised - a meaningful limiter that CVSS does not fully model. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker lures a target to a crafted HTML page (phishing link, malvertising, or watering-hole) that first triggers a separate GPU-process vulnerability to gain code execution inside the GPU sandbox. From that foothold, the page invokes WebRTC APIs to trigger the out-of-bounds read, leaking heap layout and then shaping allocations to drive heap corruption - used as the next link in a sandbox-escape chain toward renderer or browser-process compromise. … |
| Remediation | Vendor-released patch: Google Chrome 149.0.7827.103 (stable channel) - upgrade all desktop installs per the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0153744567.html and track upstream details via the Chromium issue tracker entry at https://issues.chromium.org/issues/514671098. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Identify Chrome deployment scope across the organization and enable automatic updates if not already active. …
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
EUVD-2026-35267
GHSA-wx6h-3mh7-h885