Cached-audio disclosure via metadata-omitting cache key
Published Jun 3, 2026 · Updated Jun 3, 2026
Cache-key collision in Gradio before 6.15.1 allows local users to make distinct audio outputs share a cache namespace. The save_audio_to_cache function hashes only NumPy array bytes, omitting sample rate, format, dtype, and shape, so non-equivalent audio resolves to the same directory. Successful exploitation requires low-privileged local access and matched raw sample bytes; the record reports limited disclosure with no integrity or availability effect.
Summary
What happened
Cache-key collision in Gradio before 6.15.1 allows local users to make distinct audio outputs share a cache namespace. The save_audio_to_cache function hashes only NumPy array bytes, omitting sample rate, format, dtype, and shape, so non-equivalent audio resolves to the same directory. Successful exploitation requires low-privileged local access and matched raw sample bytes; the record reports limited disclosure with no integrity or availability effect.
The record
- CVE
- CVE-2026-10783
- Published
- Jun 3, 2026
- Updated
- Jun 3, 2026
- Vendor
- Gradio
- Product
- Gradio
- Classifications
- CWE-328, CWE-327, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 3, 2026CVE publishedPublication date reported by the CVE source.
- Jun 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.14.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Audio cache-key collision reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo