Live Active security incident? Get immediate response
CVE Record

CVE-2026-9915: Heap buffer overflow in ANGLE in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who had co...

Heap buffer overflow in ANGLE in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

HighCVSS 8.3Not KEV-listed Updated
Glexia's Take high

Analyst readout for executives and security teams

Plain-English summary

This Chrome flaw affects ANGLE, a graphics component. If an attacker already compromises Chrome’s renderer, a crafted HTML page could help escape the browser sandbox, turning a browser compromise into broader system risk. The source bundle does not show active exploitation.

Executive priority

Treat as a high-priority browser patching item. The sandbox-escape impact is serious, but the available evidence does not support emergency active-exploitation claims.

Technical view

CVE-2026-9915 is a CWE-122 heap buffer overflow in ANGLE in Google Chrome before 148.0.7778.216. The CVSS 3.1 score is 8.3 with network attack vector, high attack complexity, required user interaction, changed scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Organizations with Google Chrome versions earlier than 148.0.7778.216 are the relevant exposure group. Risk is highest where browser patching lags or users routinely browse untrusted web content.

Exploitation context

The CVE requires a compromised renderer process and user interaction with a crafted HTML page. KEV status is false in the supplied bundle, and no cited source states active exploitation.

Researcher notes

This issue is only described at a high level publicly: ANGLE heap overflow, renderer compromise prerequisite, sandbox escape potential. Avoid assuming a standalone remote code execution path without additional vendor detail.

Mitigation direction

  • Update Google Chrome to 148.0.7778.216 or later.
  • Prioritize managed desktop fleets and high-risk user groups.
  • Check Google’s Chrome release guidance for any platform-specific instructions.
  • Keep browser auto-update policies enabled and monitored.

Validation and detection

  • Inventory Chrome versions across managed endpoints.
  • Confirm installed versions are 148.0.7778.216 or later.
  • Review patch compliance dashboards for lagging systems.
  • Monitor vendor advisories for updates to exploit or mitigation status.
Prepared
Confidence
high
Sources
4

Based on public source material and reviewed before publication.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-122: 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 lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-9915 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profile CVE Program record
Severity
High
CVSS
8.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

Official CVE source material

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.

1 CVSS vectors
3 Timeline events
1 ADP providers
3 Source links

SSVC decision data

CISA-ADP CISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We 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.

Score Version Severity Vector Exploit Impact Source
8.3 CVSS 3.1 High CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H 1.6 6 CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

8.3 High
CVSS 3.1 vector shape for CVE-2026-9915 Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reserved CVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE published CVE Program

    The CVE record was published.

  3. CVE updated CVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADP CISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

Vendor Product Version / package Status
Google Chrome 148.0.7778.216 Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-122 · source CWE mapping

Heap-based Buffer Overflow

Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.