Skip to main content
VulnerabilityPublished Updated

CVE-2024-48052: gradio · Server-Side Request Forgery (SSRF)

Affects gradioSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
PyPIgradiopkg:pypi/gradioOther threatsAffected
  • <=4.42.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-48052, organizations should first upgrade Gradio to a version where this vulnerability is patched once available. Until an official patch is released, consider the following specific actions: 1) Implement strict input validation and URL allowlisting on any user-supplied URLs processed by gr.DownloadButton or related functions to restrict requests to trusted domains only. 2) Employ network-level controls such as firewall rules or egress filtering to prevent the Gradio server from making outbound requests to internal or sensitive network segments. 3) Run Gradio services with the least privilege necessary, limiting access to sensitive files and internal resources. 4) Monitor application logs for unusual or unexpected URL requests that could indicate exploitation attempts. 5) If feasible, isolate the Gradio server in a segmented network zone with restricted access to internal resources. 6) Educate developers and administrators about SSRF risks and secure coding practices to prevent similar vulnerabilities. 7) Conduct regular security assessments and penetration tests focusing on SSRF and related vulnerabilities in web applications.

Description

In gradio <=4.42.0, the gr.DownloadButton function has a hidden server-side request forgery (SSRF) vulnerability. The reason is that within the save_url_to_cache function, there are no restrictions on the URL, which allows access to local target resources. This can lead to the download of local resources and sensitive information.

References

Community reviews

Loading reviews…