EUVD-2026-50630
GHSA-pqxg-9927-553c
Severity by source
Sources disagree (Medium–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Remote crafted page (AV:N/AC:L/PR:N) requires the victim to visit it (UI:R); renderer memory-corruption RCE gives full C/I/A but stays sandboxed, so S:U.
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
5DescriptionCVE.org
Integer overflow in WebXR in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Sandboxed remote code execution in Google Chrome's WebXR implementation (all channels prior to 151.0.7922.72) lets a remote attacker run arbitrary code within the renderer sandbox when a victim visits a crafted HTML page. Google rates the Chromium security severity as Medium, though the CVSS 8.8 reflects high impact contingent on user interaction; no public exploit identified at time of analysis and EPSS is low (0.22%, 13th percentile). …
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 actively browse to attacker-controlled content using a vulnerable Chrome build (before 151.0.7922.72) - UI:R in the CVSS vector confirms required user interaction, so this is not a zero-click or server-side attack. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8) indicates a low-complexity, unauthenticated network attack requiring user interaction (visiting a page), with high confidentiality, integrity, and availability impact but no scope change - consistent with the description's note that execution stays 'inside a sandbox.' Counterbalancing signals lower the real-world priority: Google's own Chromium severity is only Medium, EPSS is 0.22% (13th percentile), the vulnerability is NOT on CISA KEV, and no public exploit is identified. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker hosts a malicious web page containing crafted WebXR content and lures a victim running a pre-151.0.7922.72 Chrome build to visit it (via phishing link, malvertising, or a compromised site). When the page loads, the crafted WebXR data triggers the integer overflow / memory-corruption condition, giving the attacker arbitrary code execution inside the renderer sandbox. … |
| Remediation | Vendor-released patch: 151.0.7922.72 - update Google Chrome to 151.0.7922.72 or later (Stable channel) and restart the browser to load the fix; managed fleets should confirm auto-update is enabled or push the update via enterprise policy. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, issue a security advisory to all Chrome users and IT teams; inventory Chrome deployment methods and establish current version baseline across managed and unmanaged devices. …
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 Use After Free
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today