VulnerabilityPublished 17 Sep 2026

CVE-2026-93387: Google Chrome · Improper State Validation

Affects Google ChromeSource CVE Database V5

Compare

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

Data as of 1 Nov 2026, 22:58 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 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 153.0.8010.52

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 17 Sep 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 1 Nov 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.

ghsa-h2gx-2wp9-ghcx

What to do

Upgrade Google Chrome to 153.0.8010.52.

Affected software

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

AI-suggested

A stable channel update for Google Chrome has been released to fix this vulnerability. Users should update to version 153.0.8010.52 or later to mitigate this issue. No additional action is required beyond applying the official update.

Description

CVE-2026-93387 is a medium severity vulnerability in Google Chrome prior to version 153.0.8010.52 involving improper state validation in the Skia component. This flaw could allow a remote attacker to obtain cross-origin data by tricking a user into visiting a crafted HTML page. The vulnerability does not allow integrity or availability impacts, but it compromises confidentiality to a limited extent. Google has released a stable channel update to address this issue.

Impact

A remote attacker can exploit this vulnerability to access cross-origin data that should normally be protected by the browser's same-origin policy. This results in limited confidentiality loss but does not affect data integrity or availability. There are no known exploits in the wild at this time.

Summary

An improper state validation vulnerability exists in the Skia graphics library used by Google Chrome before version 153.0.8010.52. This vulnerability allows a remote attacker to bypass same-origin policy restrictions and obtain cross-origin data by delivering a specially crafted HTML page to a victim. The issue is classified with a CVSS score of 4.3 (medium severity) and affects confidentiality only, without impacting integrity or availability.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Sep 2026, 04:20 UTC

Technical details

References

Community reviews

Related threats