gradio
50 published advisories; version 6.16.0 or later fixes all but 11 of them.
- Registry
- PyPI
- Advisories
- 50
- Latest fix
- 6.16.0
- Exploited in the wild
- None listed
11 advisories have no fixed release in any version yet. What can be done meanwhile:
General guidance from ShieldPi, not a vendor fix
- Path traversal. Limit the folders it can reach at the operating-system level, such as a container or a user with access to only those folders, and keep credentials and keys outside them.GHSA-pgfv-gvc5-prfg · GHSA-prpg-p95c-32fv
- Server-side request forgery. Restrict its outbound network access to the hosts it needs, and keep internal addresses and cloud metadata endpoints out of its reach.GHSA-3gf9-wv65-gwh9 · GHSA-973g-55hp-3frw
Check your projects
shieldpi agent-config checks agent and MCP packages from npm and PyPI, not gradio. Any scanner that reads the OSV database finds it in your lockfiles, for example Google's open-source OSV-Scanner.
osv-scanner scan source -r .Or check a lockfile against ShieldMap in your browser.
Packages reported malicious by OpenSSF whose names imitate gradio. Check that you install gradio itself.
- graddio 1 letter off
Source: github.com/gradio-app/gradio, named in the package metadata (not verified)
10 of the last 10 releases of gradio were published with build provenance: a signed record of the repository and commit each was built from, which the registry checks before it accepts the release.
- 6.32.0
- 6.31.0
- 6.30.0
- 6.29.1
- 6.29.0
- 6.28.0
- 6.27.0
- 6.26.0
- 6.25.0
- 6.24.0
Green: published with provenance. Grey: without.
OpenSSF Scorecard: 5.9 of 10 on 2026-11-16.
- No dangerous CI workflows
- 10/10
- CI tokens read-only by default
- 0/10
- Build dependencies pinned
- 0/10
- Branch protection
- Not checked
- Changes reviewed before merge
- 8/10
- Signed releases
- Not checked
- Actively maintained
- 10/10
- Security policy
- 10/10
Provenance from deps.dev (CC BY 4.0); Scorecard from OpenSSF (CDLA-Permissive-2.0). As of 2026-11-18.
Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].