VulnerabilityPublished 20 May 2026

CVE-2026-9113: Google Chrome · Out-of-bounds Read

Affects Google ChromeSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 148.0.7778.179 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 148.0.7778.179

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Google Chrome to 148.0.7778.179.

Affected software

Product	Affected	Fixed in
GoogleChrome	Affected >=148.0.7778.179 <148.0.7778.179	Fixed in 148.0.7778.179

AI-suggested

Users should update Google Chrome on Mac to version 148.0.7778.179 or later, where this vulnerability has been fixed. The vendor advisory confirms the availability of this stable channel update. No additional mitigation actions are indicated by the vendor.

Description

CVE-2026-9113 is a medium severity vulnerability in Google Chrome on Mac platforms prior to version 148.0.7778.179. It involves an out of bounds read in the GPU component triggered by a crafted HTML page, which could allow a remote attacker to read memory beyond intended boundaries. The vulnerability does not impact integrity or availability and requires user interaction to exploit. There are no known exploits in the wild. A stable channel update addressing this issue was released by Google.

Impact

The vulnerability allows a remote attacker to perform an out of bounds read of memory on affected Chrome versions on Mac, potentially exposing limited information from memory. There is no impact on data integrity or system availability. Exploitation requires user interaction (visiting a crafted HTML page). No known active exploits have been reported.

Summary

This vulnerability is an out of bounds memory read in the GPU subsystem of Google Chrome on Mac systems before version 148.0.7778.179. An attacker can craft a malicious HTML page that, when visited by a user, causes the browser to read memory outside of its allocated bounds. The CVSS 3.1 base score is 4.3, reflecting low impact on confidentiality and no impact on integrity or availability, with no privileges required and user interaction needed. The issue was publicly disclosed and fixed in Chrome version 148.0.7778.179. The vendor advisory linked confirms a stable channel update addressing this vulnerability.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 May 2026, 21:03 UTC

Technical details

References

Community reviews

Related threats