Vulnerability in gradio (CVE-2026-10783)
Summary
Vulnerability in gradio (CVE-2026-10783). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 6.15.1 or later.
Original description
The description as published by the source.
A security flaw has been discovered in gradio-app gradio 6.14.0. This affects the function save_audio_to_cache of the component Audio Cache Key Handler. Performing a manipulation results in use of weak hash. The attack must be initiated from a local position. The attack is considered to have high complexity. It is indicated that the exploitability is difficult. The exploit has been released to the public and may be used for attacks. The patch is named 13394. To fix this issue, it is recommended to deploy a patch.
Source: GitHub Security Advisories (Global) 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-10783 has been found in gradio.
Risk of unauthorized operations or information disclosure. CVSS score: 2.5/10.
What to do: upgrade gradio to 6.15.1 or later.
If unsure, ask your IT team or search "gradio CVE-2026-10783" on the vendor's site.
CVE-2026-10783 (gradio) — CWE-327 / CVSS v3 2.5
Attack vector: local / no user interaction
Patched: 6.15.1 — 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.
A vulnerability (CWE-327) exists in gradio.
Check the vendor advisory for the affected versions of gradio.
Severity: Low (CVSS 2.5/10). Risk of unauthorized operations or information disclosure.
Update to 6.15.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
grep -r 'gradio' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
gradioを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade gradio to 6.15.1ステージング環境で 6.15.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory vuldb.com
- advisory vuldb.com
- advisory vuldb.com
- advisory github.com
- package github.com
- patch github.com
- report github.com
- report vuldb.com
- web github.com
- web github.com
- web github.com