EUVD-2026-65832
GHSA-q7wp-j2m3-5x8v
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Renderer pre-compromise modeled as AC:H; no Chrome-level authentication needed (PR:N); user must load the page (UI:R); pure sensor data disclosure with no integrity or availability impact.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Lifecycle Timeline
4DescriptionCVE.org
Missing authorization in Sensor in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to obtain sensitive information via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Sensor API information disclosure in Google Chrome before 152.0.7977.65 enables a remote attacker who has already compromised the renderer process to read sensitive device sensor data by loading a crafted HTML page. The flaw (CWE-862, Missing Authorization) does not provide initial access on its own - it is a post-exploitation primitive that extends the capability of a pre-existing renderer compromise. …
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 two mandatory preconditions: (1) the attacker must have already achieved code execution within Chrome's renderer process via a separate, independently sourced renderer vulnerability - this CVE alone provides no initial access; and (2) user interaction is required (CVSS UI:R), meaning the target user must navigate to or load a crafted HTML page. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N scores 5.3 (Medium). … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first exploits a separate renderer-level vulnerability (such as a V8 engine or Blink flaw) to gain code execution within Chrome's sandboxed renderer process on the victim's machine. From the compromised renderer, the attacker sends unauthorized requests to the Sensor component - bypassing the missing authorization check - to read device sensor telemetry (e.g., gyroscope, accelerometer readings) via a crafted HTML page. … |
| Remediation | The primary fix is to upgrade Google Chrome to version 152.0.7977.65 or later, available via Chrome's built-in updater (chrome://settings/help) or from Google's official download channel. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-862 – Missing Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today