VulnerabilityPublished 30 Jul 2026

CVE-2026-17870: Google Chrome · Insufficient Validation of Untrusted Input

Affects Google ChromeSource CVE Database V5

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

Data as of 28 Oct 2026, 05:11 UTC

CVSS 3.1 base score

4.3Medium

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

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

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

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

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

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
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: None: The vulnerable system can be exploited without any interaction from any user.
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 30 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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 151.0.7922.72.

Affected software

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

AI-suggested

The vendor has released a stable channel update for desktop Chrome as referenced in the advisory URL. Users should update to version 151.0.7922.72 or later to remediate this vulnerability. Patch status is not explicitly confirmed in the provided data; therefore, users should consult the vendor advisory for the latest remediation guidance.

Description

CVE-2026-17870 is a medium severity vulnerability in Google Chrome prior to version 151.0.7922.72. It involves insufficient validation of untrusted input in the Cast component, which could allow an attacker on the local network segment to leak cross-origin data via malicious network traffic. This vulnerability does not allow privilege escalation or denial of service but impacts confidentiality. No known exploits are reported in the wild. The vendor has published an advisory but has not explicitly stated the remediation status in the provided data.

Impact

An attacker on the local network segment can leak cross-origin data, potentially exposing sensitive information. There is no impact on integrity or availability. The vulnerability is limited to confidentiality exposure and does not allow code execution or privilege escalation.

Summary

This vulnerability in Google Chrome's Cast feature arises from insufficient validation of untrusted input. An attacker positioned on the same local network segment could exploit this flaw to leak cross-origin data by sending malicious network traffic. The issue affects versions prior to 151.0.7922.72. The CVSS v3.1 base score is 4.3, reflecting a medium severity with local network attack vector, low attack complexity, no privileges required, no user interaction, unchanged scope, and impact limited to confidentiality loss.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Aug 2026, 17:22 UTC

Technical details

References

Community reviews

Related threats