dbcve.org
ChromeWeb browser · Google

CVE-2023-2721

HIGH · 8.8 CVSS v3.1 Published 2023-05-16
Fix available
A fix is available. Upgrade to 113.0.5672.126 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 Navigation in Google Chrome prior to 113.0.5672.126 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)

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

Use-after-free vulnerability in Chrome's navigation component that allows a remote attacker to access freed memory, potentially leading to heap corruption and remote code execution via a crafted HTML page.

MitigationUpdate Google Chrome to version 113.0.5672.126 or later to apply the security patch.

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:< 113.0.5672.126
Debian LinuxOperating system
Affected:= 11.0
FedoraOperating system
Affected:= 37= 38

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 if Google Chrome is installed
    Run: which google-chrome or ls /usr/bin/google-chrome* on Linux systems. On Windows, check Program Files/Google/Chrome/Application/
    Affected if Google Chrome browser is present on the system
  2. Determine installed Chrome version
    Run: google-chrome --version or about:version in Chrome address bar
    Affected if Version is lower than 113.0.5672.126 (for example, 113.0.5672.92 or earlier)
  3. Verify Linux distribution if Chrome from distro repos
    Check /etc/os-release or run: cat /etc/os-release | grep VERSION_ID for Debian; cat /etc/fedora-release for Fedora
    Affected if Running Debian 11, Fedora 37, or Fedora 38 with Chrome installed from system repositories

User is affected if Google Chrome is installed and its version is below 113.0.5672.126, or if Chrome was installed via Debian 11, Fedora 37, or Fedora 38 package repositories.

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

Update Google Chrome to version 113.0.5672.126 or later to apply the security patch.

Recommended fix High confidence

Chrome/Chromium 113.0.5672.126 or later

  1. Update Chrome/Chromium to version 113.0.5672.126 or later
  2. For Debian Linux: Run 'apt-get update && apt-get upgrade' to install the latest chromium package
  3. For Fedora: Run 'dnf update' to install the latest chromium package
  4. Restart the browser after applying the update

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
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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