ChromeWeb browser · Google
CVE-2024-7966
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOut of bounds memory access in Skia in Google Chrome prior to 128.0.6613.84 allowed a remote attacker who had compromised the renderer process to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOut of bounds memory access vulnerability in Skia's graphics rendering library within Google Chrome's renderer process. Exploitable via crafted HTML page, but requires the renderer process to already be compromised (indicating this is likely a secondary exploit for privilege escalation or sandbox escape). Fixed in Chrome 128.0.6613.84.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
< 128.0.6613.84CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Chrome versionOpen Chrome, click the three-dot menu > Help > About Google Chrome, or navigate to chrome://versionAffected if The displayed version is lower than 128.0.6613.84
-
Verify version via command lineOn Windows, run 'reg query "HKEY_CURRENT_USER\Software\Google\Chrome\BLBeacon" /v version' or check Program Files\Google\Chrome\Application\chrome.exe properties. On macOS, run 'defaults read /Applications/Google\ Chrome.app/Contents/Info CFBundleVersion'Affected if The retrieved version number is less than 128.0.6613.84
-
Confirm renderer sandbox status (optional context)Navigate to chrome://sandbox in Chrome and check that 'Sandbox: Enabled' is reported for renderer processesAffected if Sandbox is disabled (does not mean vulnerability exists, but increases exploit severity)
A user is affected if their installed Chrome version is below 128.0.6613.84, as this is where the Skia out-of-bounds memory access in the renderer process was fixed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped128.0.6613.84
Update Google Chrome to version 128.0.6613.84 or later. For enterprise environments, deploy the update via patch management systems. This is a renderer-process vulnerability, so ensure Chrome's sandbox is enabled and renderer process isolation is not disabled.
Chrome 128.0.6613.84
- Open Chrome and navigate to Help > About Google Chrome to check the current version
- If the version is less than 128.0.6613.84, click 'Update Google Chrome' to download and install the latest version
- Restart Chrome browser to complete the update
- Verify the update was successful by returning to Help > About Google Chrome and confirming version 128.0.6613.84 or later is installed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7966 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-7966 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data