Live Active security incident? Get immediate response
CVE Record

CVE-2026-9907: Out of bounds read in Dawn in Google Chrome on Windows prior to 148.0.7778.216 allowed a remote attacker to...

Out of bounds read in Dawn in Google Chrome on Windows prior to 148.0.7778.216 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)

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

Analyst readout for executives and security teams

Plain-English summary

Chrome on Windows had a memory-read flaw in the Dawn component. A malicious web page could potentially expose limited cross-origin data from a user’s browser. The issue requires user interaction and is scored medium by CVSS, although Chromium labels the security severity High.

Executive priority

Treat this as a prompt browser patching item, not a crisis absent exploitation evidence. Organizations with delayed Chrome updates or sensitive browser workflows should accelerate remediation and verify fleet coverage.

Technical view

CVE-2026-9907 is a CWE-125 out-of-bounds read in Dawn affecting Google Chrome on Windows prior to 148.0.7778.216. The CVSS vector indicates network attack, low complexity, no privileges, required user interaction, unchanged scope, and low confidentiality impact only.

Likely exposure

Exposure is mainly Windows endpoints running Google Chrome before 148.0.7778.216, especially unmanaged devices or fleets with delayed browser updates. The source bundle does not identify other affected products or platforms.

Exploitation context

The bundle does not show KEV listing or cited evidence of active exploitation. The described attack path is a crafted HTML page that a user must load, with potential cross-origin data leakage. No exploit details are provided.

Researcher notes

Validation should focus on version and platform exposure rather than exploit reproduction. Public details are limited in the bundle, and the Chromium issue reference does not provide enough evidence here to infer exploit maturity or additional mitigations.

Mitigation direction

  • Update Chrome on Windows to 148.0.7778.216 or later.
  • Confirm enterprise browser update policies are enforcing the fixed channel.
  • Check Google Chrome release guidance for any additional vendor instructions.
  • Prioritize unmanaged Windows endpoints and users with high-risk browsing exposure.

Validation and detection

  • Inventory Windows Chrome versions across managed and unmanaged endpoints.
  • Flag any Chrome installation older than 148.0.7778.216.
  • Confirm update telemetry after browser restart, not just package deployment.
  • Review exposure for users handling sensitive browser-accessible data.
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-125: 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-9907 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
4.3 (3.1)
Known Exploited
No
Published

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

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
4.3 CVSS 3.1 Medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N 2.8 1.4 CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.