Analyst readout for executives and security teams
Plain-English summary
This Chrome flaw is a memory safety bug in proxy handling. A user interaction path involving a crafted PAC script could let an attacker run code in the browser process. Because Chrome is widely deployed and Chromium rates it Critical, enterprises should treat outdated desktop Chrome as urgent.
Executive priority
Prioritize remediation within normal emergency browser patch timelines. The business risk is broad endpoint exposure to browser code execution, but the provided sources do not prove active exploitation.
Technical view
CVE-2026-9887 is a CWE-416 use-after-free in Chrome Proxy before 148.0.7778.216. The published description says arbitrary code execution is possible through a crafted PAC script. The CVSS vector requires user interaction and is scored 7.8, while Chromium severity is Critical.
Likely exposure
Exposure is mainly desktop Chrome installations older than 148.0.7778.216, especially systems using PAC or proxy auto-configuration. The bundle does not identify other Chromium-based browsers or platforms as affected.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Public details are limited; the Chromium issue may restrict technical details. Treat exploitability as plausible but unconfirmed from these sources.
Researcher notes
The core issue is use-after-free in Proxy, reachable via crafted PAC script. Evidence does not include exploit mechanics, affected CPEs, or downstream Chromium browser impact. Note the bundle’s affected field is sparse, while the description clearly says prior to 148.0.7778.216.
Mitigation direction
- Update Google Chrome to 148.0.7778.216 or later through managed update channels.
- Verify auto-update policies are enabled and reporting current versions.
- Review enterprise PAC/proxy auto-configuration sources for trust and change control.
- Prioritize high-risk users who browse externally or use managed proxy settings.
- Monitor Google Chrome release guidance for follow-up fixes or clarifications.
Validation and detection
- Inventory Chrome desktop versions and flag versions below 148.0.7778.216.
- Confirm patched endpoints report the expected stable channel version or later.
- Check browser management telemetry for failed or deferred updates.
- Review proxy/PAC configuration ownership and recent changes.
- Track CISA KEV and Google advisories for exploitation-status updates.
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-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-9887 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
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/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:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H 1.8 5.9 CISA-ADP Vulnerability scoring details
Base CVSS 3.1 score
7.8 HighVector: CVSS:3.1/AV:L/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/511249104 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.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.