Gradio has a one-level read path traversal in `/custom_component`

TRUNG BÌNH 5.3CVE-2024-47166 · GHSA-37qc-qgx6-9xjv · PYSEC-2024-197 · Công bố 10/10/2024 · cập nhật 17/06/2026

Tóm tắt nhanh

CVE-2024-47166 là lỗ hổng mức TRUNG BÌNH (CVSS 5.3) ảnh hưởng gradio, gradio (gradio project).
Xác suất bị khai thác trong 30 ngày tới (EPSS): 0.44%, cao hơn 37.9% các lỗ hổng khác.
Cách xử lý: cập nhật lên 4.44.0 hoặc mới hơn.

Gói / sản phẩm	Phiên bản bị ảnh hưởng	Phiên bản đã vá
gradio PyPI	`< 4.44.0`	`4.44.0`
gradio gradio_project	`< 4.44.0`	`4.44.0`

Mô tả

Impact

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.

Patches

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

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.

Mô tả của NVD

Gradio 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.