CVE-2024-47166

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

As a workaround, developers can sanitize the file paths and ensure that components are not stored in publicly accessible directories.

What kind of vulnerability is it? Who is impacted?

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.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2024-47166 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.44.0); upgrading removes the vulnerable code path.

Kodem intelligence

Yes, please upgrade to gradio>=4.44 to address this issue.

1. What is CVE-2024-47166? CVE-2024-47166 is a medium-severity path traversal vulnerability in gradio (pip), affecting versions < 4.44.0. It is fixed in 4.44.0. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2024-47166? CVE-2024-47166 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of gradio are affected by CVE-2024-47166? gradio (pip) versions < 4.44.0 is affected.
4. Is there a fix for CVE-2024-47166? Yes. CVE-2024-47166 is fixed in 4.44.0. Upgrade to this version or later.
5. Is CVE-2024-47166 exploitable, and should I be worried? Whether CVE-2024-47166 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-47166 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-47166? Upgrade gradio to 4.44.0 or later.