PatchSiren cyber security CVE debrief
CVE-2026-17905 Google CVE debrief
CVE-2026-17905 is a medium-severity vulnerability in Google Chrome prior to version 151.0.7922.72, caused by an inappropriate implementation in SurfaceCapture. This issue allows a remote attacker to leak cross-origin data via a crafted HTML page. The vulnerability affects Google Chrome deployments, and defenders should assess exposure and prioritize patching to prevent potential data leaks. The CVE record and NVD entry provide details on the vulnerability, its severity, and affected versions.
- 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 Google Chrome deployments should assess exposure and prioritize patching to prevent potential data leaks. This includes reviewing and updating incident response plans, monitoring for potential data leaks, and verifying and applying the patch to Google Chrome. The vulnerability affects Google Chrome prior to version 151.0.7922.72, and defenders should take immediate action to prevent exposure
Why it matters
CVE-2026-17905 is a medium-severity vulnerability in Google Chrome that allows a remote attacker to leak cross-origin data. Defenders should prioritize verifying and applying the patch to prevent potential data leaks.
- Data leak prevention is crucial to protect sensitive information.
- Verifying and applying the patch is essential to prevent exploitation.
- Monitoring for potential data leaks is necessary to detect and respond to incidents.
Technical summary
The vulnerability is caused by an inappropriate implementation in SurfaceCapture in Google Chrome prior to version 151.0.7922.72. This allows a remote attacker to leak cross-origin data via a crafted HTML page. The issue affects Google Chrome deployments, and defenders should assess exposure and prioritize patching to prevent potential data leaks. The CVE record and NVD entry provide details on the vulnerability, its severity, and affected versions.
Defensive priority
Defenders should prioritize verifying and applying the patch to prevent potential data leaks.
Recommended defensive actions
- Verify and apply the patch to Google Chrome
- Monitor for potential data leaks
- Review and update incident response plans
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, its severity, and affected versions. The vulnerability is caused by an inappropriate implementation in SurfaceCapture in Google Chrome prior to version 151.0.7922.72. This allows a remote attacker to leak cross-origin data via a crafted HTML page. Defenders should verify and apply the patch to prevent potential data leaks. The source detail is limited, and defenders should expand with explicit evidence-limit language.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-17905 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-17905
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-17905 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-17905
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/497366217
[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.