Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious HTML page exploiting Geolocation leak
-
ExploitSocial engineer victim to visit page in Chrome
-
ExecutionGeolocation API triggered without proper consent
-
ImpactVictim's precise location data exfiltrated to attacker
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the victim to actively visit a crafted HTML page - user interaction (UI:R) is mandatory and social engineering is the described delivery mechanism, meaning passive drive-by exploitation without user navigation is not possible. The victim must be running Google Chrome prior to version 152.0.7977.65 on any desktop platform. The attacker requires no authentication or elevated privileges (PR:N). Exploitation is further limited by the browser's geolocation permission system; if the flaw relies on bypassing the permission prompt, users who have previously denied geolocation to all sites may be less exposed - however, the exact bypass mechanism is not publicly confirmed. No special server-side configuration or non-default Chrome settings are described as prerequisites. |
| Impact | CVSS 6.5 with vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N classifies this as medium severity. The C:H rating reflects that geolocation data is highly sensitive personal information capable of revealing home and workplace locations. However, UI:R is a meaningful constraint - exploitation is gated on successful social engineering to direct the victim to a malicious page. EPSS at 0.21% (11th percentile) strongly suggests this is not being opportunistically or widely exploited. There is no CISA KEV listing and no confirmed POC. The combination of a high confidentiality impact with a low exploitation probability and mandatory user interaction places this as a genuine privacy risk warranting prompt patching but not emergency response escalation. No conflicting signals detected: CVSS, EPSS, and KEV status are mutually consistent in painting a moderate-priority, socially-engineered information disclosure. |
| Exploit ScenarioDerived | An attacker registers a convincing phishing domain and hosts a crafted HTML page that exploits the Geolocation information leak in Chrome. The attacker sends a targeted phishing email or social media message directing the victim to the page; when the victim loads it in an unpatched version of Chrome, the attacker silently receives the victim's precise geolocation coordinates. No public POC has been identified, but the low technical complexity (AC:L) and social engineering delivery model make targeted attacks feasible for motivated actors. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 26, 2026
Information disclosure in Google Chrome's Geolocation component prior to version 152.0.7977.65 allows a remote attacker to obtain the victim's sensitive geolocation data by tricking them into visiting a crafted HTML page. The attack relies on social engineering as the delivery mechanism and results in a high-confidentiality-impact leak of physical location information, which may expose home or workplace addresses. No public exploit code or active exploitation has been identified; EPSS at 0.21% (11th percentile) confirms low automated exploitation probability at time of analysis.
RemediationAI
Update Google Chrome to version 152.0.7977.65 or later per the stable channel update advisory at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. Chrome's auto-update mechanism should deliver this automatically; verify by navigating to chrome://settings/help. For enterprise environments, enforce the minimum version via policy (ChromeManagement or GPO) and confirm deployment via fleet management tooling. As a compensating control pending update, administrators can disable or restrict Geolocation API access site-wide using the DefaultGeolocationSetting enterprise policy set to 2 (Block), though this will break legitimate geolocation-dependent web applications. Instructing users not to grant geolocation permissions to unfamiliar sites reduces exposure but does not eliminate the risk if the flaw bypasses the permission prompt entirely.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability resides in Chrome's Geolocation API subsystem - the browser component that mediates web content requests for the device's physical position via GPS, Wi-Fi triangulation, or IP geolocation. CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) indicates the flaw allows crafted HTML to access or leak geolocation data outside the intended trust boundary, likely circumventing or bypassing normal user consent or permission-prompt mechanisms. The affected CPE is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, covering all Chrome desktop builds before 152.0.7977.65. The Chromium issue tracker reference (issues.chromium.org/issues/533093250) is non-public, so the precise internal mechanism - whether a race condition, improper permission check, or API mishandling - cannot be independently confirmed from available data.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
Sources disagree (Medium–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Network delivery via crafted page, no privileges required, user must interact; geolocation leak is high confidentiality impact with no integrity or availability effect.
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
Lifecycle Timeline
3DescriptionCVE.org
Information leak in Geolocation in Google Chrome prior to 152.0.7977.65 allowed a remote attacker leveraging social engineering to obtain sensitive information via a crafted HTML page. (Chromium security severity: Medium)
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Same weakness CWE-200 – Information Exposure
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
EUVD-2026-66007
GHSA-f4fr-6hpc-v792
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB