# CVE-2026-10783: gradio-app gradio Audio Cache Key save_audio_to_cache weak hash

> A local attacker with high complexity can exploit a weak hash in Gradio's audio cache, potentially compromising cache integrity.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Jun 2026
- **Updated:** 4 Jun 2026
- **Also known as:** GHSA-6655-8ph2-63j3, PYSEC-2026-211

## What is CVE-2026-10783?

CVE-2026-10783 is a low-severity vulnerability in Gradio Project Gradio, published on 3 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-328 (Use of Weak Hash), CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2026-10783?

3 open source packages ship an affected version, including gradio. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gradio` | PyPI | All versions to 6.14.0 | None |
| `gradio` | PyPI | All versions | 6.15.1 |
| `gradio` | PyPI | All versions | 6.15.1 |

Products: Gradio Project Gradio.

## How do I fix CVE-2026-10783?

Upgrade gradio to 6.15.1 or later.

## Is CVE-2026-10783 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10783 exists.

## Other vulnerabilities in Gradio Project Gradio

- [CVE-2024-39236](https://insights.sbomify.com/CVE-2024-39236/): Withdrawn Advisory: Gradio was discovered to contain a code injection vulnerability via the component /gradio/component_meta.py (critical 9.8)
- [CVE-2023-6572](https://insights.sbomify.com/CVE-2023-6572/): Command Injection in gradio-app/gradio (critical 9.6)
- [CVE-2022-24770](https://insights.sbomify.com/CVE-2022-24770/): Improper Neutralization of Formula Elements in a CSV File in Gradio Flagging (high 8.8)
- [CVE-2026-49119](https://insights.sbomify.com/CVE-2026-49119/): Gradio < 6.16.0 Path Traversal via FileExplorer.preprocess() (high 8.7)
- [CVE-2025-23042](https://insights.sbomify.com/CVE-2025-23042/): Gradio Blocked Path ACL Bypass Vulnerability (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10783 and fix it if it is affected.

What it is: CVE-2026-10783 is a low-severity vulnerability in Gradio Project Gradio, published on 3 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10783 exists.

Affected packages and fixed versions:
- gradio (PyPI): affected all versions up to 6.14.0; no fix listed
- gradio (PyPI): affected all versions; fixed in 6.15.1
- gradio (PyPI): affected all versions; fixed in 6.15.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10783/ (Markdown: https://insights.sbomify.com/CVE-2026-10783/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10783
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10783
- OSV: https://osv.dev/vulnerability/CVE-2026-10783

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10783/
Summaries are generated and may contain mistakes; the official description above is the record.