dbcve.org
ChromeWeb browser · Google

CVE-2023-5186

HIGH · 8.8 CVSS v3.1 Published 2023-09-28
Fix available
A fix is available. Upgrade to 117.0.5938.132 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 Passwords in Google Chrome prior to 117.0.5938.132 allowed a remote attacker who convinced a user to engage in specific UI interaction to potentially exploit heap corruption via crafted UI interaction. (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

A use-after-free vulnerability exists in the Passwords functionality of Google Chrome versions prior to 117.0.5938.132. The flaw allows a remote attacker who tricks a user into specific UI interactions to potentially exploit heap corruption by accessing freed memory, leading to possible code execution or further heap corruption.

MitigationUpdate Google Chrome to version 117.0.5938.132 or later. Organizations should ensure automated browser patching is enabled and users are notified to restart their browsers.

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

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 Google Chrome version
    Navigate to chrome://settings/help or run 'google-chrome --version' in terminal
    Affected if Version is older than 117.0.5938.132
  2. Verify Chrome is being used on an affected OS
    Check OS version with 'cat /etc/os-release' (Debian 11/12) or 'cat /etc/fedora-release' (Fedora 37/38/39)
    Affected if Running Debian 11, Debian 12, Fedora 37, Fedora 38, or Fedora 39 with an affected Chrome version
  3. Confirm Passwords sync or storage feature is active
    Check if user has enabled password saving in Chrome settings at chrome://settings/passwords
    Affected if Password saving is enabled and Chrome version is vulnerable
  4. Check for Chrome package origin on Linux
    Inspect installed package with 'dpkg -l | grep google-chrome' (Debian) or 'rpm -qi google-chrome' (Fedora)
    Affected if Chrome package version is below 117.0.5938.132 regardless of install source

User is affected if running Google Chrome version below 117.0.5938.132 on Debian 11/12 or Fedora 37/38/39 with Passwords feature enabled or synced.

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

Update Google Chrome to version 117.0.5938.132 or later. Organizations should ensure automated browser patching is enabled and users are notified to restart their browsers.

Recommended fix High confidence

Chrome 117.0.5938.132 or later (or the corresponding patched chromium package versions in Debian/Fedora repositories)

  1. For Chrome Desktop users: Open Chrome and navigate to Settings → About Chrome (or go to chrome://settings/help) to trigger automatic update checking, or download the latest version from google.com/chrome
  2. For Debian Linux systems: Run 'sudo apt update && sudo apt upgrade' to receive the security update for the chromium package
  3. For Fedora Linux systems: Run 'sudo dnf update' to receive the security update for the chromium package
  4. Restart the browser after updating to ensure the vulnerability is fully mitigated

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-2023-5186 — 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-5186 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