PatchSiren cyber security CVE debrief
CVE-2026-17954 Google CVE debrief
A policy bypass vulnerability in MHTML in Google Chrome prior to 151.0.7922.72 allows a remote attacker to leak cross-origin data via a crafted MHTML page. This issue is considered to have a medium severity with a CVSS score of 4.3. The vulnerability affects Google Chrome installations and could lead to potential data leaks. Defenders should verify and update Google Chrome to version 151.0.7922.72 or later to prevent potential data leaks. The CVE record and NVD vulnerability detail page provide information on the policy bypass vulnerability in MHTML in Google Chrome. The Chromium security severity is considered Low. To address this vulnerability, defenders should prioritize updates
- Vendor
- Product
- Chrome
- CVSS
- MEDIUM 4.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-30
- Original CVE updated
- 2026-10-23
- Advisory published
- 2026-07-30
- Advisory updated
- 2026-10-23
Who should care
Defenders responsible for managing and updating Google Chrome installations should prioritize verifying and updating to version 151.0.7922.72 or later to prevent potential data leaks.
Why it matters
Defenders should prioritize verifying and updating Google Chrome to version 151.0.7922.72 or later to prevent potential data leaks due to the policy bypass vulnerability in MHTML.
- Data leaks due to cross-origin data exposure
- Potential for unauthorized access to sensitive information
- Need for verification and updates to Google Chrome
Technical summary
The policy bypass vulnerability in MHTML in Google Chrome prior to 151.0.7922.72 allows a remote attacker to leak cross-origin data via a crafted MHTML page. The CVSS score is 4.3, and the Chromium security severity is considered Low. This vulnerability affects Google Chrome installations and could lead to potential data leaks. To mitigate this vulnerability, defenders should verify and update Google Chrome to version 151.0.7922.72 or later. The update will help prevent potential data leaks due to the policy bypass vulnerability in MHTML. Additionally, defenders
Defensive priority
Defenders should prioritize verifying and updating Google Chrome to version 151.0.7922.72 or later to prevent potential data leaks.
Recommended defensive actions
- Verify and update Google Chrome to version 151.0.7922.72 or later
- Monitor Google Chrome for any potential security updates
- Review and implement secure coding practices for MHTML pages
Evidence notes
The CVE record and NVD vulnerability detail page provide information on the policy bypass vulnerability in MHTML in Google Chrome. The Chromium security severity is considered Low.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-17954 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-17954
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-17954 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-17954
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html
[email protected] - Release Notes, Vendor Advisory
-
Source reference
Unverified legacy reference
URL: https://issues.chromium.org/issues/517383492
[email protected] - Permissions Required
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.