dbcve.org
ChromeWeb browser · Google

CVE-2024-7000

HIGH · 8.8 CVSS v3.1 Published 2024-08-06
Fix available
A fix is available. Upgrade to 127.0.6533.72 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Use after free in CSS in Google Chrome prior to 127.0.6533.72 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)

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 confidence

A use-after-free vulnerability exists in the CSS rendering component of Google Chrome versions prior to 127.6533.72. An attacker can craft a malicious HTML page that, when rendered after specific user UI interactions, causes the browser to access freed memory, potentially leading to heap corruption and arbitrary code execution.

MitigationUpdate Google Chrome to version 127.6533.72 or later to patch the CSS use-after-free vulnerability. Organizations should deploy browser updates through their patch management systems and verify completion across affected endpoints.

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
Affected:< 127.0.6533.72

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Chrome version
    Open Chrome and navigate to chrome://version, or run 'google-chrome --version' (Linux) or check 'C:\Program Files\Google\Chrome\Application\chrome.exe --version' (Windows) in command prompt
    Affected if the displayed version number is less than 127.0.6533.72
  2. Verify Chrome browser is actively in use
    Check for running Chrome processes using Task Manager (Windows), Activity Monitor (macOS), or 'ps aux | grep chrome' (Linux)
    Affected if Chrome browser processes are currently running and the version from step 1 is below 127.0.6533.72
  3. Confirm Chrome is the default or primary browser
    Check system default browser settings, or review recently accessed files and browser history for Chrome activity
    Affected if Chrome is set as default or shows recent usage history and the version is vulnerable
  4. Identify Chrome installation location
    On Windows check registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome, or on Linux check /usr/bin/google-chrome or /opt/google/chrome
    Affected if Chrome installation is found and version check from step 1 shows a version prior to 127.0.6533.72

A user is affected if Google Chrome is installed and running with any version prior to 127.0.6533.72, as the use-after-free vulnerability in the CSS rendering component can be triggered through crafted HTML pages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 127.0.6533.72 or later
Fixed in 127.0.6533.72
Interim mitigation

Update Google Chrome to version 127.6533.72 or later to patch the CSS use-after-free vulnerability. Organizations should deploy browser updates through their patch management systems and verify completion across affected endpoints.

Recommended fix High confidence

127.0.6533.72 or later

  1. Open Google Chrome browser
  2. Click the three-dot menu icon in the top-right corner
  3. Select 'Help' from the dropdown menu
  4. Click 'About Google Chrome'
  5. Chrome will automatically check for and install any available updates
  6. Restart the browser if an update is installed
  7. Confirm the version is 127.0.6533.72 or later by checking About Google Chrome again

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7000 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-7000 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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