← Back
CVE-2025-23042
Vulnerability in gradio (CVE-2025-23042)
Summary
vulnerability in gradio (CVE-2025-23042). Confidential information can be exposed externally. Exploitable via ``blocked_paths``. Mitigation: upgrade to `5.11.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-23042** has been found in gradio.
Attackers can target a specific entry point like ``blocked_paths`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade gradio to **5.11.0** or later.
If unsure, ask your IT team or search "gradio CVE-2025-23042" on the vendor's site.
CVE-2025-23042 (gradio) — CWE-178 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `blocked_paths` / `is_in_or_equal` / `resources` / `admin`
Patched: `5.11.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-178) exists in gradio. Attackers reach the vulnerable code path via ``blocked_paths`` without authentication.
📍 Affected scope
gradio — . Attack surface: `blocked_paths` / `is_in_or_equal` / `resources` / `admin`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **5.11.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'gradio' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'gradio' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `gradio` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade gradio to 5.11.0ステージング環境で 5.11.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
gradio
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.11.0"}]}]
pip
gradio
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.11.0"}]}]
References
- advisory https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/23xxx/CVE-2025-23042.json
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-23042
- package https://github.com/gradio-app/gradio
- web https://github.com/gradio-app/gradio/security/advisories/GHSA-j2jg-fq62-7c3h
- web https://github.com/gradio-app/gradio/commit/6b63fdec441b5c9bf910f910a2505d8defbb6bf8
- web https://github.com/gradio-app/gradio/releases/tag/gradio%405.11.0
- web https://github.com/pypa/advisory-database/tree/main/vulns/gradio/PYSEC-2025-118.yaml
- web https://github.com/advisories/GHSA-j2jg-fq62-7c3h