Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-9966 Overview
CVE-2024-9966 is a Content Security Policy (CSP) bypass vulnerability in Google Chrome's Navigations component. The flaw affects Chrome versions prior to 130.0.6723.58 and stems from an inappropriate implementation that allows a remote attacker to bypass CSP restrictions through a crafted HTML page. Google rated the Chromium security severity as Low. The issue was addressed in the Stable channel update released on October 15, 2024. CSP bypasses weaken a core browser defense against cross-site scripting and data injection attacks, allowing attackers to execute content that the page author intended to block.
Critical Impact
A remote attacker can bypass Content Security Policy protections on affected Chrome versions by serving a crafted HTML page, undermining a key defense-in-depth control against script injection.
Affected Products
- Google Chrome versions prior to 130.0.6723.58
- Chromium-based browsers inheriting the vulnerable Navigations implementation
- Desktop Chrome Stable channel on Windows, macOS, and Linux
Discovery Timeline
- 2024-10-15 - Google releases Chrome 130.0.6723.58 to the Stable channel addressing the issue
- 2024-10-15 - CVE-2024-9966 published to NVD
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-9966
Vulnerability Analysis
The vulnerability resides in Chrome's Navigations component, which governs how the browser handles page transitions, redirects, and sub-resource loads. Google's advisory classifies the issue as an inappropriate implementation that fails to properly enforce Content Security Policy during certain navigation flows. CSP is a declarative allowlist mechanism that restricts the origins from which scripts, styles, frames, and other resources can load. When navigation logic skips or misapplies these checks, attacker-controlled content can execute outside the policy boundary. NVD assigns the issue CWE classification NVD-CWE-noinfo because Google has not published root-cause specifics. The impact is scoped to integrity, with no direct confidentiality or availability loss documented.
Root Cause
The root cause is an implementation defect in how the Navigations code path evaluates CSP directives during specific transitions. Chromium issue 364773822 tracks the underlying defect but access is restricted pending wider patch adoption. The fix landed in Chrome 130.0.6723.58.
Attack Vector
Exploitation requires a victim to visit an attacker-controlled or compromised web page. The attacker crafts HTML that triggers the vulnerable navigation path, causing the browser to load or execute content that the site's CSP header would normally block. No authentication or user interaction beyond page navigation is required. There are no public proof-of-concept exploits, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog.
No verified exploit code is available. See the Chromium Issue Report #364773822 for the tracking entry.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2024-9966
Indicators of Compromise
- Browser telemetry showing script or frame loads from origins not permitted by a page's declared CSP
- CSP violation reports that stop arriving from pages where violations were previously observed, indicating silent bypass
- Outbound connections from browser processes to attacker infrastructure following navigation to untrusted sites
Detection Strategies
- Deploy CSP report-to and report-uri endpoints to collect violation reports and detect anomalies in reporting coverage
- Inventory Chrome versions across managed endpoints and flag any instance below 130.0.6723.58
- Correlate web proxy logs with browser version data to identify users on vulnerable builds visiting untrusted domains
Monitoring Recommendations
- Monitor endpoint management tooling for Chrome update compliance and auto-update health
- Track browser process network connections for unexpected destinations following page loads
- Review CSP violation report volume and investigate significant drops that may indicate bypass
How to Mitigate CVE-2024-9966
Immediate Actions Required
- Update Google Chrome to version 130.0.6723.58 or later on all desktop endpoints
- Verify Chromium-based browsers in the environment have incorporated the upstream fix
- Enforce browser auto-update policies through enterprise management tools such as Chrome Browser Cloud Management or Group Policy
Patch Information
Google addressed the vulnerability in the Stable channel update released October 15, 2024. See the Google Chrome Stable Update for release notes. Users should confirm they are running Chrome 130.0.6723.58 or newer by navigating to chrome://settings/help.
Workarounds
- No vendor-supplied workaround exists; patching is the only reliable remediation
- Restrict browsing to trusted sites via web proxy allowlists until patches are deployed
- Combine CSP with additional controls such as Trusted Types and Subresource Integrity to reduce the impact of CSP bypasses
# Verify installed Chrome version on Linux or macOS
google-chrome --version
# Expected output must be 130.0.6723.58 or later
# Chrome 130.0.6723.58
# Windows: query the installed version via registry
reg query "HKLM\SOFTWARE\Google\Chrome\BLBeacon" /v version
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

