Analyst readout for executives and security teams
Plain-English summary
This is a high-severity Chrome browser flaw. A remote attacker could make a user open a crafted web page and potentially run arbitrary code through Chrome's USB implementation. The sources do not show confirmed active exploitation.
Executive priority
Prioritize this as an urgent browser patching item. The impact is potentially full code execution, but the available sources require user interaction and do not confirm active exploitation.
Technical view
CVE-2026-9976 is an inappropriate implementation issue in Chrome's USB component, mapped to CWE-94. Chrome versions prior to 148.0.7778.216 are described as affected. The CVSS 3.1 score is 8.8, with network attack vector, low complexity, no privileges required, and user interaction required.
Likely exposure
Organizations with managed or unmanaged desktop Chrome installations below 148.0.7778.216 are the primary exposure. Risk depends on users browsing attacker-controlled or compromised pages. The bundle does not identify other Chromium-based products as affected.
Exploitation context
The CVE record says exploitation requires a crafted HTML page and user interaction. KEV status is false in the bundle, and no cited source confirms active exploitation or public exploit availability.
Researcher notes
Public evidence is limited. The Chromium issue may contain restricted details, and the bundle provides no exploit technique, indicators, or non-update workaround. Avoid extending impact to other browsers without vendor confirmation.
Mitigation direction
- Update Google Chrome to 148.0.7778.216 or later.
- Check Google's Chrome release guidance for platform-specific update details.
- Prioritize managed browser patch rollout for internet-facing user workstations.
- Reduce exposure to untrusted browsing until updates are complete.
Validation and detection
- Inventory Chrome versions across managed endpoints.
- Confirm deployed Chrome versions are 148.0.7778.216 or later.
- Check browser update policy compliance in endpoint management tools.
- Review security telemetry for unusual Chrome crash or compromise indicators.
Public sources used
Based on public source material and reviewed before publication.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-9976 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H 2.8 5.9 CISA-ADP Vulnerability scoring details
Base CVSS 3.1 score
8.8 HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reserved CVE Program
The CVE ID was reserved by the assigning CNA.
- CVE published CVE Program
The CVE record was published.
- CVE updated CVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 source CVE List V5
- https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.html CVE reference, Chrome
- https://issues.chromium.org/issues/511732828 CVE reference, Chrome
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.