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 12 May 2023.
ChromeWeb browser · Google

CVE-2023-2136

CRITICAL · 9.6 CVSS v3.1 Published 2023-04-19
Fix available
A fix is available. Upgrade to 112.0.5615.137 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild 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
Integer overflow in Skia in Google Chrome prior to 112.0.5615.137 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape 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

Integer overflow vulnerability in Skia (2D graphics library) in Google Chrome allows a remote attacker with a compromised renderer process to potentially escape the sandbox via a crafted HTML page, enabling arbitrary code execution outside the sandbox.

MitigationUpdate Google Chrome to version 112.0.5615.137 or later. Organizations should also review and enforce browser update policies across endpoints.

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:< 112.0.5615.137
Debian LinuxOperating system
Affected:= 11.0
FedoraOperating system
Affected:= 36= 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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 browser version
    Open Chrome, click the three-dot menu > Help > About Google Chrome. The version number is displayed on this page.
    Affected if The installed version is earlier than 112.0.5615.137 (e.g., 112.0.5615.135 or lower).
  2. Verify Chrome installation on Linux
    Run 'google-chrome --version' or 'chromium --version' in terminal to get the installed browser version.
    Affected if The version output is lower than 112.0.5615.137.
  3. Confirm Skia library usage
    This vulnerability is in the Skia graphics library bundled with Chrome. No separate Skia installation check is needed - the vulnerability only applies through the Chrome browser.
    Affected if Chrome is installed and version is below 112.0.5615.137.
  4. Identify if Chrome is running in a vulnerable configuration
    The exploit requires a compromised renderer process. Check running Chrome processes with 'ps aux | grep chrome' to note browser is active. However, detecting a compromised renderer is not feasible through standard inspection.
    Affected if Chrome is running and its version falls below 112.0.5615.137, making exploitation possible if an attacker already has renderer code execution.

You are affected if Google Chrome is installed at any version lower than 112.0.5615.137 on Debian 11, Fedora 36, 37, or 38, or on any other operating system.

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

Update Google Chrome to version 112.0.5615.137 or later. Organizations should also review and enforce browser update policies across endpoints.

Recommended fix High confidence

Chrome 112.0.5615.137 or later (or distribution-provided package that includes this security fix)

  1. Check current Chrome version by navigating to chrome://settings/help
  2. Download and install Google Chrome 112.0.5615.137 or later from the official Google Chrome website (google.com/chrome)
  3. For Linux systems using package managers: On Debian-based systems run 'sudo apt update && sudo apt upgrade' to receive the fixed Chromium/Chrome package
  4. For Fedora systems run 'sudo dnf update' to receive the fixed Chromium package
  5. Restart the browser after installation to apply the update
Caveat Chrome stable releases typically have minimal breaking changes; however, some legacy extensions or web apps may have compatibility issues with newer versions

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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