PatchSiren cyber security CVE debrief
CVE-2026-17674 Google CVE debrief
The CVE-2026-17674 vulnerability is caused by an inappropriate implementation in HTML in Google Chrome prior to version 151.0.7922.72. This allows a remote attacker to bypass content security policy via a crafted HTML page. The vulnerability has a CVSS score of 6.5 and is classified as MEDIUM severity. The Chromium security team has rated this as High severity. Affected users should apply the official patch to update Google Chrome to version 151.0.7922.72 or later. IT administrators responsible for managing Google Chrome deployments should verify and enforce content security policy in their organization's Chrome deployments. Users of Google Chrome prior to version 151.0.7922.72 should monitor Chrome browser versions and ensure all instances are up-to-date.
- Vendor
- Product
- Chrome
- CVSS
- MEDIUM 6.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-30
- Original CVE updated
- 2026-08-10
- Advisory published
- 2026-07-30
- Advisory updated
- 2026-08-10
Who should care
IT administrators responsible for managing Google Chrome deployments, security teams monitoring for potential content security policy bypasses, and users of Google Chrome prior to version 151.0.7922.72 should be aware of this vulnerability and take necessary actions to prevent potential bypass of content security policy.
Technical summary
The CVE-2026-17674 vulnerability is caused by an inappropriate implementation in HTML in Google Chrome prior to version 151.0.7922.72. This allows a remote attacker to bypass content security policy via a crafted HTML page. The vulnerability has a CVSS score of 6.5 and is classified as MEDIUM severity. The Chromium security team has rated this as High severity. The vulnerability affects Google Chrome deployments, and IT administrators should verify and enforce content security policy in their organization's Chrome deployments.
Defensive priority
Medium severity vulnerability in Google Chrome, requiring immediate attention to prevent potential bypass of content security policy.
Recommended defensive actions
- Apply the official patch to update Google Chrome to version 151.0.7922.72 or later.
- Verify and enforce content security policy in your organization's Chrome deployments.
- Monitor Chrome browser versions and ensure all instances are up-to-date.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
Evidence notes
The CVE-2026-17674 record indicates an inappropriate implementation in HTML in Google Chrome prior to 151.0.7922.72, allowing a remote attacker to bypass content security policy via a crafted HTML page. Chromium security severity is High, with a CVSS score of 6.5 and severity of MEDIUM. The official CVE record and NVD detail page provide additional information on the vulnerability. The source item URL used to retrieve CVE-2026-17674 information is also relevant. Defenders should verify the affected scope, severity, and vendor guidance.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-17674 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-17674
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-17674 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-17674
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
-
Source reference
Unverified legacy reference
URL: https://issues.chromium.org/issues/513791232
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.