dbcve.org
ChromeWeb browser · Google

CVE-2024-11113

HIGH · 8.8 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 131.0.6778.69 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 Accessibility in Google Chrome prior to 131.0.6778.69 allowed a remote attacker who had compromised the renderer process 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 Google Chrome's Accessibility component prior to version 131.0.6778.69. An attacker who has already compromised the renderer process can exploit this flaw via a specially crafted HTML page to achieve heap corruption, potentially leading to arbitrary code execution.

MitigationUpdate Google Chrome to version 131.0.6778.69 or later. Organizations should deploy the update through their patch management systems and verify completion across all managed 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:< 131.0.6778.69

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. Check installed Chrome version
    Open Chrome, click the three-dot menu > Help > About Google Chrome. The version number is displayed on this page.
    Affected if The version shown is less than 131.0.6778.69 (for example, 131.0.6778.64 or any earlier version).
  2. Check Chrome version via command line
    On Windows, open Command Prompt and run: chrome --version. On macOS, run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version. On Linux, run: google-chrome --version.
    Affected if The reported version is below 131.0.6778.69.
  3. Verify Accessibility component status
    In Chrome, go to Settings > Accessibility (or search 'accessibility' in settings). Confirm the feature is enabled or has been used at least once, as this activates the vulnerable code path.
    Affected if Accessibility has been enabled or accessed, making the attack surface active.
  4. Check if Chrome is running in a potentially exposed mode
    Determine if Chrome is running with remote debugging enabled (--remote-debugging-port flag) or as part of an automated test/headless environment, which could increase renderer exposure.
    Affected if Chrome is running with developer debugging flags or in an automated testing environment where the renderer process may be more accessible.

You are affected if Chrome version is below 131.0.6778.69 and the Accessibility feature has been enabled or used on the browser profile.

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 131.0.6778.69 or later
Fixed in 131.0.6778.69
Interim mitigation

Update Google Chrome to version 131.0.6778.69 or later. Organizations should deploy the update through their patch management systems and verify completion across all managed endpoints.

Recommended fix High confidence

Chrome 131.0.6778.69 or later (version 131 stable release)

  1. Open Google Chrome and navigate to Menu (three dots) > Help > About Google Chrome
  2. Check if the current version is below 131.0.6778.69
  3. If an update is available, click 'Update Google Chrome' to download and install the fix
  4. Restart Chrome completely to apply the update
  5. Verify the version now shows 131.0.6778.69 or later under Menu > Help > About Google Chrome

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11113 — 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-11113 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