dbcve.org
ChromeWeb browser · Google

CVE-2023-4763

HIGH · 8.8 CVSS v3.1 Published 2023-09-05
Fix available
A fix is available. Upgrade to 116.0.5845.179 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 Networks in Google Chrome prior to 116.0.5845.179 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 confidence

Use-after-free vulnerability in Google Chrome's Networks component allows a remote attacker to exploit heap corruption via a maliciously crafted HTML page. The vulnerability exists because memory is accessed after being freed, leading to potential arbitrary code execution.

MitigationUpdate Google Chrome to version 116.0.5845.179 or later to patch the vulnerability.

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:< 116.0.5845.179
Debian LinuxOperating system
Affected:= 11.0= 12.0

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 or Chromium is installed
    Open terminal and run: google-chrome --version OR chromium --version
    Affected if No version output means the browser is not installed and is not affected
  2. Verify the exact Chrome version number
    Navigate to chrome://settings/help in the browser or run google-chrome --version in terminal
    Affected if Version displays as less than 116.0.5845.179
  3. Check Chromium version on Debian systems
    Run dpkg -l | grep chromium or apt show chromium on Debian 11/12 systems
    Affected if Installed Chromium version is earlier than 116.0.5845.179-1~deb11u1 or 116.0.5845.179-1~deb12u1 respectively
  4. Confirm the Networks component feature is in use
    This vulnerability affects the Networks component - any user visiting a malicious HTML page while using Chrome/Chromium could trigger the flaw
    Affected if Using Chrome/Chromium version below 116.0.5845.179 and browsing untrusted web pages

A system is affected if Google Chrome or Chromium is installed with a version lower than 116.0.5845.179, since the use-after-free flaw in the Networks component can be triggered by visiting a maliciously crafted HTML page.

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

Update Google Chrome to version 116.0.5845.179 or later to patch the vulnerability.

Recommended fix High confidence

Chrome 116.0.5845.179 or later (stable release)

  1. Open Chrome browser and navigate to Settings > Help > About Google Chrome
  2. Verify the current version and ensure Chrome automatically checks for updates
  3. If update available, click 'Update Google Chrome' and restart the browser
  4. Alternatively, download the latest Chrome stable build from the official Google Chrome download page (google.com/chrome) and install it
  5. For Debian Linux systems with Chrome installed, run: sudo apt update && sudo apt upgrade google-chrome-stable (for Debian 12) or ensure the installed Chrome version is 116.0.5845.179 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 / QA0.5 h
3.5 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-4763 — 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-4763 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