Skip to main content
EPSS 0.2%top 92%

CVE-2026-17901: Inappropriate implementation in Google Chrome

0
Medium
VulnerabilityCVE-2026-17901cvecve-2026-17901
Published: 07/30/2026 (07/30/2026, 00:19:52 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Chrome

Description

Insufficient validation of untrusted input in Sharing in Google Chrome on Android prior to 151.0.7922.72 allowed a remote attacker to bypass navigation restrictions via malicious network traffic. (Chromium security severity: Low)

CVSS v3.1

Score 4.3medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Affected software

Google

Chrome

Affected versions
>=151.0.7922.72 <151.0.7922.72
GitHub Actionsmore threats →ai
chromium/chromium
pkg:github/chromium/chromium
Affected versions
<151.0.7922.72

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 08/06/2026, 16:36:27 UTC

Technical Analysis

This vulnerability arises from improper input validation in the Sharing functionality of Google Chrome on Android. An attacker can exploit this flaw by sending malicious network traffic that bypasses navigation restrictions, potentially leading to limited unauthorized actions. The issue is tracked as CWE-20 (Improper Input Validation). The vulnerability affects Chrome on Android versions before 151.0.7922.72. There is no explicit vendor advisory stating a patch or remediation level, but the affected version indicates that 151.0.7922.72 is the fixed version.

Potential Impact

The impact is limited to bypassing navigation restrictions, which may allow an attacker to influence navigation behavior in the browser. There is no confidentiality or availability impact reported. The overall severity is medium with no known exploits in the wild.

Mitigation Recommendations

Users should update Google Chrome on Android to version 151.0.7922.72 or later to remediate this vulnerability. Patch status is not explicitly confirmed in the vendor advisory, but the affected version data indicates this version includes the fix. No additional mitigation steps are specified by the vendor.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Chrome
Date Reserved
2026-07-27T23:35:15.471Z
State
PUBLISHED
Vendor Advisory Urls
[{"url":"https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html","vendor":"Google"}]

Threat ID: 6a6aa0a29c2644c7f849b939

Added to database: 07/30/2026, 00:53:54 UTC

Last enriched: 08/06/2026, 16:36:27 UTC

Last updated: 09/11/2026, 19:31:53 UTC

Views: 45

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses