Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-48545 medium CVSS 6.8

Vulnerability in gradio (CVE-2026-48545)

Summary

Vulnerability in gradio (CVE-2026-48545). Confidential information can be exposed externally. Mitigation: upgrade to 6.15.0 or later.

Original description

The description as published by the source.

Gradio before version 6.15.0 contains a cookie injection vulnerability that allows remote attackers to perform cross-Space session fixation by exploiting a shared module-level HTTP client used across all users in the reverse proxy endpoint. Attackers controlling any HF Space can return a parent-domain cookie that the shared client stores and automatically replays into all subsequent proxy requests to other legitimate Spaces, affecting all users of the same Gradio deployment.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-48545 has been found in gradio.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: upgrade gradio to 6.15.0 or later.
If unsure, ask your IT team or search "gradio CVE-2026-48545" on the vendor's site.

CVE-2026-48545 (gradio) — CWE-384 / CVSS v3 6.8
Attack vector: remote (network-reachable) / unauthenticated
Patched: 6.15.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-384) exists in gradio.

📍 Affected scope

Check the vendor advisory for the affected versions of gradio.

🔥 Severity

Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 6.15.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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'gradio' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で gradio を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade gradio to 6.15.0

    ステージング環境で 6.15.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip gradio
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.15.0"}]}]
PyPI gradio
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.15.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details