CVE-2026-8517
Google Chrome ≤ 148.0.7778.168
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2026-8517 is a high-severity Improper Control of a Resource Through its Lifetime (CWE-664) vulnerability in Google Chrome. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Process Injection (T1055); ranked at the 40th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-39 (Process Isolation) and SC-4 (Information in Shared System Resources) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-30431
Vulnerability Data
Object lifecycle issue in WebShare in Google Chrome on Mac prior to 148.0.7778.168 allowed a remote attacker who convinced a user to engage in specific UI gestures to execute arbitrary code via a crafted HTML page. (Chromium security severity: Critical)
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 4 hardening rules · 3 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
SC-39 enforces separate execution domains so one process cannot corrupt or misuse another process's resources across their lifetimes.
SC-4 prevents unintended information transfer through shared resources, limiting blast radius when a product fails to release or reuse resources correctly.
SI-16 blocks unauthorized code execution in memory, stopping exploitation that commonly follows improper allocation, use-after-free, or deallocation errors.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Directly requires managing assets through creation, use, and disposal phases, preventing lifetime control failures.
Enforces consistent configuration and handling rules that reduce improper resource lifetime management.
Integrates secure practices across the full development lifecycle, addressing resource creation-to-release control.
Covers ongoing maintenance and removal of software, indirectly limiting resource lifetime issues.
Addresses hardware maintenance and replacement phases that intersect with resource lifetime control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Information deletion control ensures proper release and sanitization at end of life.
Secure SDLC embeds resource lifecycle controls from design through decommissioning.
Secure architecture principles reduce lifetime control issues but are not specific to them.
Secure coding practices help avoid lifetime control bugs but do not address the full scope.
Configuration management enforces lifecycle rules for resource creation, use and disposal.
Backups preserve resources but do not govern their full lifetime control.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Windows Server 2016 (2 rules)
- V-224971 The Active Directory SYSVOL directory must have the proper access control permissions. prevents CWE-664
- V-224970 Permissions on the Active Directory data files must only allow System and Administrators access. prevents CWE-664
Windows Server 2019 (1 rule)
- V-205739 Windows Server 2019 permissions on the Active Directory data files must only allow System and Administrators access. prevents CWE-664