Nixpkgs Security Tracker

Login with GitHub

Details of issue NIXPKGS-2026-0507

NIXPKGS-2026-0507
published on 3 Mar 2026
Permalink CVE-2026-28416
8.2 HIGH
  • CVSS version: 3.1
  • Attack vector (AV): NETWORK
  • Attack complexity (AC): LOW
  • Privileges required (PR): NONE
  • User interaction (UI): NONE
  • Scope (S): UNCHANGED
  • Confidentiality impact (C): HIGH
  • Integrity impact (I): LOW
  • Availability impact (A): NONE
updated 2 weeks, 6 days ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    8 packages
    • python312Packages.gradio-pdf
    • python313Packages.gradio-pdf
    • python314Packages.gradio-pdf
    • pkgsRocm.python3Packages.gradio-client
    • pkgsRocm.python3Packages.gradio-pdf
    • python314Packages.gradio-client
    • python313Packages.gradio-client
    • python312Packages.gradio-client
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Gradio has SSRF via Malicious `proxy_url` Injection in `gr.load()` Config Processing

Gradio is an open-source Python package designed for quick prototyping. Prior to version 6.6.0, 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. Version 6.6.0 fixes the issue.

Affected products

gradio
  • ==< 6.6.0

Matching in nixpkgs

Ignored packages (8)

Package maintainers

Upstream advisory: https://github.com/gradio-app/gradio/security/advisories/GHSA-jmh7-g254-2cq9