CVE-2026-10783: Gradio weak hash in save_audio_to_cache audio caching

CVE-2026-10783 · Severity: low · CVSS 3.1 · Published 2026-06-04

Gradio is an open-source Python library used to build web interfaces for machine learning models. A security flaw in its audio caching system allows different audio files with identical raw data but different settings (like sample rate or format) to be stored in the same location. This could potentially allow a local user to access or overwrite cached audio data belonging to other sessions, leading to minor data exposure or incorrect file delivery.

Technologies: gradio (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-10783 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-10783 being exploited in the wild.
How severe is CVE-2026-10783?
Low severity, with a CVSS score of 3.1, published 4 June 2026.
Which products and versions are affected?
gradio (PyPI) < 6.15.1, ECOSYSTEM:introduced=0,fixed=6.15.1, ECOSYSTEM:introduced=0,last_affected=6.14.0.
Is there a fix for CVE-2026-10783?
Yes. gradio (PyPI): upgrade to 6.15.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-10783 attacked?
It is attacked with local access, in a software library.
Am I affected by CVE-2026-10783?
Check whether you run gradio (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • gradio (PyPI): upgrade to 6.15.1 or later
    pip install "gradio>=6.15.1"

Technical details

A vulnerability in the `save_audio_to_cache` function of Gradio's Audio Cache Key Handler results in the use of a weak hash for cache directory naming. The implementation derives the cache key solely from raw audio bytes (`data.tobytes()`), ignoring critical metadata such as sample rate, format, dtype, and shape. Consequently, two different audio outputs with identical raw sample bytes but different interpretation metadata resolve to the same cache namespace. An attacker with local access could exploit this collision to cause the application to serve incorrect cached audio files or potentially access data from a different context. The issue is addressed in version 6.15.1 by including metadata in the cache key generation.

Affected products

  • gradio-app gradio < 6.15.1

Identifiers

  • CVE-2026-10783
  • GHSA-6655-8ph2-63j3
  • PYSEC-2026-211

Timeline

  • 2026-05-16: disclosed: Issue reported on GitHub
  • 2026-05-26: patched: Fix merged into main branch
  • 2026-06-04: advisory: GitHub Advisory and CVE published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.