dbcve.org
GradioApplication · Gradio Project

CVE-2023-25823

CRITICAL · 9.8 CVSS v3.1 Published 2023-02-23
Fix available
A fix is available. Upgrade to 3.13.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Gradio is an open-source Python library to build machine learning and data science demos and web applications. Versions prior to 3.13.1 contain Use of Hard-coded Credentials. When using Gradio's share links (i.e. creating a Gradio app and then setting `share=True`), a private SSH key is sent to any user that connects to the Gradio machine, which means that a user could access other users' shared Gradio demos. From there, other exploits are possible depending on the level of access/exposure the Gradio app provides. This issue is patched in version 3.13.1, however, users are recommended to update to 3.19.1 or later where the FRP solution has been properly tested.

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

Gradio versions prior to 3.13.1 contain a hardcoded SSH private key that is exposed to any user connecting to a Gradio machine when share links are enabled (share=True). This allows any user to access other users' shared Gradio demos and potentially escalate privileges based on the app's access level.

MitigationUpgrade Gradio to version 3.13.1 or later (recommended 3.19.1+) to remove the hardcoded SSH credentials from the share link functionality.

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
GradioApplication
Affected:< 3.13.1

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 Gradio version
    Run 'pip show gradio' or 'pip list | grep gradio' to see the installed version number
    Affected if Version is lower than 3.13.1 (e.g., 3.10.x, 3.9.x, etc.)
  2. Identify if share functionality is used
    Search your Gradio application code for 'share=True' in any Block launch calls, or check runtime configuration for share=True settings
    Affected if share=True is present in the application code or configuration
  3. Locate hardcoded SSH private key
    Search the Gradio package files for the string 'ssh-rsa' or 'BEGIN RSA PRIVATE KEY' within the installed gradio directory (typically in site-packages/gradio)
    Affected if A file containing an SSH private key with header 'ssh-rsa' or 'BEGIN RSA PRIVATE KEY' is found in the Gradio package directory
  4. Inspect network traffic from share links
    If you have access to a running Gradio app with share=True, capture the HTTP traffic or inspect the JavaScript loaded by the share link page for the string 'ssh-rsa' or PEM-formatted private key content
    Affected if The share link page serves or references an embedded SSH private key

You are affected if you run Gradio version lower than 3.13.1 AND use share=True to generate share links, as this combination exposes the hardcoded SSH private key to any user with the share URL.

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

Upgrade Gradio to version 3.13.1 or later (recommended 3.19.1+) to remove the hardcoded SSH credentials from the share link functionality.

Recommended fix High confidence

gradio>=3.19.1 (with minimum fixed version 3.13.1)

  1. 1. Identify the current installed version of Gradio by running: pip show gradio | grep Version
  2. 2. Upgrade Gradio to version 3.19.1 or later using: pip install --upgrade gradio>=3.19.1
  3. 3. Verify the upgrade was successful by running: pip show gradio | grep Version
  4. 4. If using share=True in Gradio apps, test that share links work correctly with the new version

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

Fix this in Gradio Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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