GradioApplication · Gradio Project
CVE-2024-47166
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 · uneditedGradio is an open-source Python package designed for quick prototyping. This vulnerability involves a **one-level read path traversal** in the `/custom_component` endpoint. Attackers can exploit this flaw to access and leak source code from custom Gradio components by manipulating the file path in the request. Although the traversal is limited to a single directory level, it could expose proprietary or sensitive code that developers intended to keep private. This impacts users who have developed custom Gradio components and are hosting them on publicly accessible servers. Users are advised to upgrade to `gradio>=4.44` to address this issue. As a workaround, developers can sanitize the file paths and ensure that components are not stored in publicly accessible directories.
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 confidenceGradio versions before 4.44 contain a path traversal vulnerability in the `/custom_component` endpoint where an attacker can manipulate file paths to read source code from custom components. The flaw allows reading files one directory level above the intended component directory, potentially exposing proprietary or sensitive developer code.
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
< 4.44.0CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Gradio versionRun 'pip show gradio' or check your requirements.txt/poetry.lock for the gradio package versionAffected if The installed version is lower than 4.44.0 (e.g., 4.43.0, 4.40.0, etc.)
-
Verify custom component endpoint is accessibleCheck if your Gradio app exposes the /custom_component route by reviewing your app's URL routing or testing access to that endpointAffected if The /custom_component endpoint responds and accepts file path parameters
-
Confirm custom components are in useInspect your project for custom component directories or files (typically under a 'custom_components' folder or similar), or check if any third-party custom components are installedAffected if Custom components are installed or loaded by your application
-
Test for path traversal exposureAttempt a request to /custom_component with path traversal sequences (e.g., ../../) to see if files outside the component directory are accessibleAffected if The endpoint returns files from parent directories or allows reading files outside the intended component directory
You are affected if you run Gradio version lower than 4.44.0, have custom components loaded, and the /custom_component endpoint is accessible without proper path validation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.44.0
Upgrade to Gradio >=4.44, or implement path validation to ensure file requests stay within allowed directories and avoid storing custom components in publicly accessible locations.
gradio>=4.44.0
- Run 'pip install --upgrade gradio' to install the latest version which includes the fix
- Verify the installation by running 'pip show gradio' and confirming the version is 4.44.0 or higher
- If using a requirements.txt or lock file, update the gradio version specification to 'gradio>=4.44.0'
- Restart any running Gradio servers to ensure the new version is loaded
- As an additional precaution, ensure custom components are not stored in publicly accessible directories
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Gradio
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47166 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-47166 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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