Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-17693: Inappropriate implementation in Google Chrome

0
High
VulnerabilityCVE-2026-17693cvecve-2026-17693
Published: 07/30/2026 (07/30/2026, 00:18:55 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Chrome

Description

CVE-2026-17693 is a high-severity vulnerability in Google Chrome prior to version 151.0.7922.72 involving insufficient policy enforcement in the FileSystem API. This flaw allows a remote attacker to leak cross-origin data by crafting a malicious HTML page. The vulnerability affects desktop versions of Chrome before the fixed release 151.0.7922.72. No CVSS score is provided, but the issue is rated high severity by Chromium security. There is no explicit vendor advisory stating the patch status, but the affected version indicates the fix is included in 151.0.7922.72. No known exploits are reported in the wild at this time.

Affected software

Affected versions
=151.0.7922.72<151.0.7922.72

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/30/2026, 02:07:27 UTC

Technical Analysis

An insufficient policy enforcement vulnerability in the FileSystem component of Google Chrome prior to version 151.0.7922.72 permits remote attackers to leak cross-origin data via a crafted HTML page. This vulnerability was publicly disclosed with high severity by Chromium security. The issue is resolved in Chrome version 151.0.7922.72. No CVSS score is assigned. The vendor advisory link references a stable channel update that presumably includes the fix.

Potential Impact

Successful exploitation allows a remote attacker to bypass same-origin policy restrictions in the FileSystem API, resulting in unauthorized cross-origin data leakage. This could compromise user data confidentiality when visiting maliciously crafted web pages.

Mitigation Recommendations

Update Google Chrome to version 151.0.7922.72 or later, which contains the fix for this vulnerability. Since this is a client-side browser issue, applying the official update is the primary mitigation. No additional vendor advisories indicate alternative mitigations or that no action is required.

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:34:24.333Z
Cvss Version
null
State
PUBLISHED
Remediation Level
null
Vendor Advisory Urls
[{"url":"https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html","vendor":"Google"}]

Threat ID: 6a6aa0829c2644c7f849a82e

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

Last enriched: 07/30/2026, 02:07:27 UTC

Last updated: 07/30/2026, 02:07:27 UTC

Views: 2

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