dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 27 Feb 2024.
ChromeWeb browser · Google

CVE-2023-4762

HIGH · 8.8 CVSS v3.1 Published 2023-09-05
Fix available
A fix is available. Upgrade to 116.0.1938.76 / 116.0.5845.179 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges Patch available

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
Type Confusion in V8 in Google Chrome prior to 116.0.5845.179 allowed a remote attacker to execute arbitrary code 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 · moderate confidence

Type Confusion vulnerability in Google Chrome's V8 JavaScript engine (versions prior to 116.0.5845.179) allows remote code execution via a specially crafted HTML page. This memory safety flaw in the JIT compiler can be exploited when a user visits a malicious webpage, potentially giving the attacker full control of the affected system.

MitigationUpdate Google Chrome to version 116.0.5845.179 or later. Organizations should deploy the update through their endpoint management systems and verify compliance.

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
FedoraOperating system
Affected:= 37= 38= 39
Edge ChromiumWeb browser
Affected:< 116.0.1938.76

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. Identify installed browser
    Open the browser and navigate to chrome://version (Chrome) or edge://version (Edge) to see the installed version, or check Add/Remove Programs in Windows Control Panel, or run 'dpkg -l' or 'rpm -qa' on Linux to list installed packages
    Affected if Google Chrome or Microsoft Edge Chromium is installed
  2. Check Google Chrome version
    In Chrome, go to Help > About Google Chrome, or run 'google-chrome --version' on Linux, or check the executable version on Windows (C:\Program Files\Google\Chrome\Application\chrome.exe)
    Affected if Version is earlier than 116.0.5845.179
  3. Check Microsoft Edge version
    In Edge, go to Help > About Microsoft Edge, or run 'msedge --version' on Linux, or check the executable version on Windows (C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe)
    Affected if Version is earlier than 116.0.1938.76
  4. Check Chrome package on Debian
    Run 'dpkg -l | grep -i chrome' or 'apt show google-chrome-stable' to see the installed package version
    Affected if Package version indicates Chrome is installed on Debian 11 or 12 and is vulnerable
  5. Check Chrome package on Fedora
    Run 'rpm -qa | grep -i chrome' to see the installed package version
    Affected if Package version indicates Chrome is installed on Fedora 37, 38, or 39 and is vulnerable

The environment is affected if Google Chrome below 116.0.5845.179 or Microsoft Edge Chromium below 116.0.1938.76 is installed and actively used, particularly on Debian 11/12 or Fedora 37/38/39 systems.

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.1938.76 / 116.0.5845.179 or later
Fixed in 116.0.1938.76116.0.5845.179
Vendor patch msrc.microsoft.com →
Interim mitigation

Update Google Chrome to version 116.0.5845.179 or later. Organizations should deploy the update through their endpoint management systems and verify compliance.

Recommended fix High confidence

Chrome 116.0.5845.179 or later; Edge 116.0.1938.76 or later; Chromium packages via distribution package managers (Debian 11/12, Fedora 37/38/39)

  1. For Chrome: Open the browser, navigate to chrome://settings/help, and click 'Update Google Chrome' if available, or the browser will auto-update on restart
  2. For Edge: Open the browser, navigate to edge://settings/help, and click 'Update Microsoft Edge' if available, or the browser will auto-update on restart
  3. For Linux systems (Debian/Fedora): Run 'sudo apt update && sudo apt upgrade' (Debian) or 'sudo dnf update' (Fedata) to update the chromium package
  4. Restart the browser after updating to ensure the vulnerability is fully mitigated
  5. Verify the version by navigating to chrome://version or edge://version to confirm the update was applied

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

Fix this in Chrome Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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