dbcve.org
GradioApplication · Gradio Project

CVE-2024-47871

CRITICAL · 9.1 CVSS v3.1 Published 2024-10-10
Fix available
A fix is available. Upgrade to 5.0.0 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 package designed for quick prototyping. This vulnerability involves **insecure communication** between the FRP (Fast Reverse Proxy) client and server when Gradio's `share=True` option is used. HTTPS is not enforced on the connection, allowing attackers to intercept and read files uploaded to the Gradio server, as well as modify responses or data sent between the client and server. This impacts users who are sharing Gradio demos publicly over the internet using `share=True` without proper encryption, exposing sensitive data to potential eavesdroppers. Users are advised to upgrade to `gradio>=5` to address this issue. As a workaround, users can avoid using `share=True` in production environments and instead host their Gradio applications on servers with HTTPS enabled to ensure secure communication.

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's share feature uses FRP (Fast Reverse Proxy) to expose demos publicly but fails to enforce HTTPS, allowing man-in-the-middle attackers to intercept uploaded files and modify client-server communication. This affects any deployment using share=True without external HTTPS termination.

MitigationUpgrade to Gradio version 5 or higher to receive the security fix. For workarounds, avoid using share=True in production and host the application behind a properly configured HTTPS-enabled reverse proxy.

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:< 5.0.0

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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 The version listed is below 5.0.0 (e.g., 4.x.x, 3.x.x)
  2. Identify Gradio applications using share=True
    Search codebase for 'share=True' in Gradio app definitions (e.g., demo = gr.Interface(..., share=True) or demo.launch(share=True))
    Affected if Any Gradio application is configured with share=True parameter enabled
  3. Check for HTTPS termination in deployment
    Inspect the deployment configuration or reverse proxy (nginx, apache, cloud provider load balancer) to verify HTTPS is enforced and traffic is properly terminated before reaching Gradio
    Affected if HTTPS is not configured on the reverse proxy/load balancer, or traffic bypasses HTTPS termination entirely
  4. Verify FRP share tunnel exposure
    When share=True is active, Gradio starts an FRP tunnel; check if the exposed URL uses HTTP (not HTTPS) by accessing the share link and inspecting the browser address bar or running 'curl -I <share_url>'
    Affected if The share URL resolves to an HTTP endpoint rather than HTTPS

A user is affected if they have Gradio version below 5.0.0 running with share=True enabled AND the share tunnel or reverse proxy does not enforce HTTPS encryption.

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

Upgrade to Gradio version 5 or higher to receive the security fix. For workarounds, avoid using share=True in production and host the application behind a properly configured HTTPS-enabled reverse proxy.

Recommended fix High confidence

gradio>=5.0.0

  1. Run 'pip install --upgrade gradio' to upgrade Gradio to version 5.0.0 or later
  2. Verify the upgrade was successful by running 'pip show gradio' and confirming the version is 5.0.0 or higher
  3. Test your Gradio application to ensure all functionality works correctly after the upgrade
Caveat Major version upgrades may introduce breaking changes; review the Gradio 5 migration documentation

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
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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