ChromeWeb browser · Google
CVE-2024-8636
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 · uneditedHeap buffer overflow in Skia in Google Chrome prior to 128.0.6613.137 allowed a remote attacker to potentially exploit heap corruption 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 confidenceA heap buffer overflow vulnerability exists in Skia, the graphics rendering library used by Google Chrome. A remote attacker can exploit this by tricking a user into visiting a crafted HTML page, potentially leading to heap corruption and possibly remote code execution. The vulnerability affects Chrome versions prior to 128.0.6613.137.
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.137CVSS 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 Chrome version in the browserOpen Chrome, click the three-dot menu, select Help, then About Google Chrome. The version number is displayed on that page.Affected if The displayed version is less than 128.0.6613.137
-
Check Chrome version via command line (Windows)Run "chrome --version" in Command Prompt or PowerShell, or right-click the Chrome shortcut and select Properties to view the version in the Target field.Affected if The reported version is less than 128.0.6613.137
-
Check Chrome version on macOSRun "/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version" in Terminal, or click Chrome > About Google Chrome from the menu bar.Affected if The reported version is less than 128.0.6613.137
-
Check Chrome version on LinuxRun "google-chrome --version" or "chromium --version" in the terminal.Affected if The reported version is less than 128.0.6613.137
You are affected if your installed Google Chrome version is any version prior to 128.0.6613.137, as the heap buffer overflow in Skia exists in those versions and can be triggered by visiting a crafted HTML page.
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.137
Update Google Chrome to version 128.0.6613.137 or later to remediate this vulnerability. No workarounds are available; users should apply the browser update promptly.
128.0.6613.137 or later (Chrome stable channel)
- Open Google Chrome and navigate to Help > About Google Chrome
- Check if the current version is less than 128.0.6613.137
- If an update is available, click 'Update Google Chrome' and restart the browser
- For enterprise environments, use administrative deployment tools to push Chrome version 128.0.6613.137 or later to all endpoints
- Verify the update was applied by checking Help > About Google Chrome shows version 128.0.6613.137 or later
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-8636 — 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-8636 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