Live Active security incident? Get immediate response
CVE Record

CVE-2026-9942: Uninitialized Use in ANGLE in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who had compr...

Uninitialized Use in ANGLE in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: High)

MediumCVSS 5Not KEV-listed Updated
Glexia's Take moderate

Analyst readout for executives and security teams

Plain-English summary

CVE-2026-9942 is a Chrome flaw in ANGLE that could let an attacker weaken site isolation after already compromising Chrome’s renderer. It requires a crafted HTML page and user interaction, so this is not a simple drive-by issue based on the provided evidence.

Executive priority

Treat this as a normal high-priority browser patch, not an emergency zero-day response from current evidence. The main business risk is exposure to chained browser attacks on outdated endpoints.

Technical view

The CVE describes CWE-457 uninitialized use in ANGLE in Google Chrome before 148.0.7778.216. A remote attacker with renderer compromise could bypass site isolation via crafted HTML. CVSS is 5.0 with high attack complexity, no privileges required, and low confidentiality, integrity, and availability impact.

Likely exposure

Organizations with managed or unmanaged desktop Chrome below 148.0.7778.216 are the relevant exposure. Risk is concentrated on endpoints where users browse untrusted web content. The CVE states user interaction is required and attack complexity is high.

Exploitation context

The source bundle does not show CISA KEV listing or cited active exploitation. The attacker must first compromise the renderer process, then use crafted HTML to bypass site isolation. That makes this more serious as part of a browser exploit chain than as a standalone vulnerability.

Researcher notes

Evidence is limited to the CVE record, Google stable-channel reference, and Chromium issue reference. The issue may have restricted details. Do not infer exploit availability, affected Chromium-based products, or operational indicators beyond the provided sources.

Mitigation direction

  • Update desktop Chrome to 148.0.7778.216 or later using Google’s stable-channel guidance.
  • Prioritize managed browser fleets and high-risk user groups first.
  • Keep browser auto-update enabled and monitor update compliance.
  • Review Google’s advisory and Chromium issue for any revised guidance.

Validation and detection

  • Inventory Chrome versions across managed and unmanaged endpoints.
  • Confirm no Chrome installations remain below 148.0.7778.216.
  • Check browser management reports for failed or deferred updates.
  • Track whether CVE-2026-9942 appears in future KEV or vendor updates.
Prepared
Confidence
medium
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-457: 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
cve · low confidence lookup

CVE-2026-9942 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
Medium
CVSS
5 (3.1)
Known Exploited
No
Published

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

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: partial

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
5 CVSS 3.1 Medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L 1.6 3.4 CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5 Medium
CVSS 3.1 vector shape for CVE-2026-9942 Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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-457 · source CWE mapping

Use of Uninitialized Variable

Use of Uninitialized Variable represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.