dbcve.org
ChromeWeb browser · Google

CVE-2023-5855

HIGH · 8.8 CVSS v3.1 Published 2023-11-01
Fix available
A fix is available. Upgrade to 119.0.6045.105 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 Reading Mode in Google Chrome prior to 119.0.6045.105 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via specific UI gestures. (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

This is a use-after-free vulnerability in Google Chrome's Reading Mode feature. A remote attacker can exploit this by tricking a user into performing specific UI gestures, potentially allowing heap corruption. The vulnerability affects Chrome versions prior to 119.0.6045.105.

MitigationUpdate Google Chrome to version 119.0.6045.105 or later. Organizations should ensure endpoint protection and browser update policies are enforced across their environment.

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:< 119.0.6045.105
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 Chrome version
    Open chrome://settings/help in the address bar, or run 'google-chrome --version' from command line
    Affected if Installed version is less than 119.0.6045.105
  2. Confirm Chrome is the active browser
    Identify which browser is used for general web browsing in your environment
    Affected if Chrome is the primary browser and version is below 119.0.6045.105
  3. Verify Reading Mode availability
    In Chrome, look for the Reading Mode icon in the address bar (appears when article content is detected) or press Alt+Shift+P on Windows/Linux or Cmd+Shift+P on macOS
    Affected if Reading Mode is accessible and Chrome version is below 119.0.6045.105
  4. Check OS version on Linux endpoints
    Run 'cat /etc/os-release' or check system information
    Affected if Running Debian 11, Debian 12, Fedora 37, Fedora 38, or Fedora 39 with Chrome version below 119.0.6045.105

Your environment is affected if Google Chrome version is below 119.0.6045.105 and users have access to the Reading Mode feature.

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

Update Google Chrome to version 119.0.6045.105 or later. Organizations should ensure endpoint protection and browser update policies are enforced across their environment.

Recommended fix High confidence

Chrome 119.0.6045.105 or later

  1. Update Google Chrome to version 119.0.6045.105 or later by navigating to Chrome Menu > Help > About Google Chrome and clicking 'Update Google Chrome'
  2. Alternatively, download the latest Chrome from the official Google Chrome website (google.com/chrome) and reinstall
  3. For Linux distributions (Debian 11/12, Fedora 37-39), update the google-chrome package via system package manager: 'sudo apt update && sudo apt upgrade google-chrome' (Debian) or 'sudo dnf update google-chrome' (Fedora)
  4. Restart the browser after updating to apply the fix
  5. Verify the version by going to chrome://settings/help - it should show version 119.0.6045.105 or higher

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-5855 — 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-5855 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