Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker registers malicious web page
-
DeliveryVictim is socially engineered to visit page in unpatched Chrome
-
ExploitCrafted JavaScript invokes FoldableAPIs cross-origin
-
ExecutionAPI returns sensitive device geometry data
-
ImpactData exfiltrated to attacker-controlled server
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 in a Chrome browser version prior to 152.0.7977.65, making user interaction (UI:R) a hard prerequisite - drive-by exploitation without a browser visit is not possible. The vulnerability is scoped to the FoldableAPIs component, which surfaces meaningful data only on foldable-form-factor devices (e.g., devices with physical fold/hinge hardware); on conventional non-foldable endpoints, the API may return empty or trivial data, materially limiting the value of any leak. No authentication is required from the attacker (PR:N in the CVSS vector). Limiting factors include the UI:R requirement, the foldable-device dependency for meaningful data exposure, and the absence of any known automated exploitation path per SSVC Automatable: no. |
| Impact | The CVSS 6.5 Medium vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) characterizes this as a low-complexity, network-reachable information disclosure requiring only a browser visit, with High Confidentiality impact - however, multiple secondary signals collectively argue for a lower real-world priority. EPSS is 0.21% at the 11th percentile, indicating very low exploitation probability relative to the broader vulnerability population. SSVC rates Exploitation: none, Automatable: no, and Technical Impact: partial, all of which are inconsistent with an imminent mass-exploitation scenario. The C:H rating in the CVSS vector conflicts with Chromium's own internal 'Low' severity classification and the SSVC 'partial' technical impact finding, suggesting the disclosed data is of limited sensitivity or real-world utility to an attacker. The UI:R requirement also prevents fully automated exploitation. The vulnerability is not in CISA KEV and no public exploit code has been identified. Overall, while the network-reachable, zero-auth attack surface warrants prompt patching in the normal Chrome update cycle, this does not meet the threshold for emergency out-of-band response for most organizations. |
| Exploit ScenarioDerived | An attacker registers or compromises a web domain and serves a crafted HTML page containing JavaScript that invokes FoldableAPIs to read cross-origin device-geometry data from the victim's unpatched Chrome browser on a foldable device. The victim is directed to the page via phishing, malvertising, or a compromised link, and upon visit the sensitive API data is silently exfiltrated to the attacker's server. No public exploit code has been identified, making opportunistic mass exploitation unlikely at this time. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 26, 2026
Cross-origin information leakage in the FoldableAPIs component of Google Chrome prior to 152.0.7977.65 enables a remote attacker to read sensitive device-geometry data from foldable-form-factor devices by luring a user to a crafted HTML page. The affected API fails to enforce origin isolation, exposing data that should be inaccessible to untrusted cross-origin scripts. No public exploit has been identified and SSVC rates exploitation status as none; Chromium's own internal severity classification of 'Low' contrasts with the NVD-assigned 6.5 Medium, reflecting the bounded real-world impact.
RemediationAI
The primary remediation is to update Google Chrome to version 152.0.7977.65 or later, which contains the vendor-released patch for this vulnerability per the Chrome stable channel advisory at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. Enterprise environments should push this update via Chrome Browser Cloud Management, Google Admin console, or equivalent MDM tooling and confirm version compliance via device inventory. Chrome's default auto-update mechanism will deliver the fix to most end users without manual intervention. No configuration-level workaround to disable FoldableAPIs independently has been identified in available data; as a compensating control prior to patching, restricting navigation to untrusted external sites via browser policy or network proxy reduces exposure, though this is operationally disruptive for general-purpose browsing environments.
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
FoldableAPIs are browser-exposed JavaScript APIs designed to surface physical characteristics of foldable-form-factor devices - such as hinge angle, screen-fold geometry, and segment dimensions - enabling responsive web experiences on devices like Samsung Galaxy Fold. The root cause is CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor): the API fails to restrict cross-origin access to device state data, allowing untrusted JavaScript to read values that should be origin-scoped or gated. The affected CPE is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, covering all Chrome versions prior to 152.0.7977.65 across platforms where the FoldableAPIs surface is present.
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
FoldableAPIs expose limited device geometry data; C:L better reflects Chromium's own Low severity rating and SSVC partial impact than the NVD-assigned C:H.
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 FoldableAPIs in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to obtain sensitive information via a crafted HTML page. (Chromium security severity: Low)
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-66062
GHSA-46w6-m262-r9xv
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB