← Back
CVE-2026-27167
Vulnerability in gradio (CVE-2026-27167)
Summary
vulnerability in gradio (CVE-2026-27167). Risk of unauthorized operations or information disclosure. Exploitable via ``gr.LoginButton``. Mitigation: upgrade to `6.6.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-27167** has been found in gradio.
Attackers can target a specific entry point like ``gr.LoginButton`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade gradio to **6.6.0** or later.
If unsure, ask your IT team or search "gradio CVE-2026-27167" on the vendor's site.
CVE-2026-27167 (gradio) — CWE-522 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `gr.LoginButton` / `HF_TOKEN` / `mocked_oauth_info` / `access_token`
Patched: `6.6.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-522) exists in gradio. Attackers reach the vulnerable code path via ``gr.LoginButton`` without authentication.
📍 Affected scope
gradio — . Attack surface: `gr.LoginButton` / `HF_TOKEN` / `mocked_oauth_info` / `access_token`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **6.6.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 6.6.0ステージング環境で 6.6.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":"4.16.0"},{"fixed":"6.6.0"}]}]
pip
gradio
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0"}]}]
References
- advisory https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/27xxx/CVE-2026-27167.json
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-27167
- package https://github.com/gradio-app/gradio
- web https://github.com/gradio-app/gradio/security/advisories/GHSA-h3h8-3v2v-rg7m
- web https://github.com/gradio-app/gradio/commit/dfee0da06d0aa94b3c2684131e7898d5d5c1911e
- web https://github.com/gradio-app/gradio/releases/tag/gradio@6.6.0
- web https://github.com/pypa/advisory-database/tree/main/vulns/gradio/PYSEC-2026-63.yaml
- web https://github.com/advisories/GHSA-h3h8-3v2v-rg7m