CVE-2026-10783: Gradio Weak Hash Vulnerability

CVE-2026-10783 Overview

CVE-2026-10783 is a weak hash vulnerability [CWE-327] affecting gradio-app/gradio version 6.14.0. The flaw resides in the save_audio_to_cache function within the Audio Cache Key Handler component. Manipulating cache key generation triggers use of a cryptographically weak hash algorithm. Exploitation requires local access and high attack complexity, limiting practical impact. Public exploit code has been released. The maintainers have published a fix tracked as patch 13394 in the upstream repository.

Critical Impact

Local attackers with low privileges can leverage weak hash collisions in audio cache key generation, potentially leading to cache poisoning or limited confidentiality impact within Gradio applications.

Affected Products

• gradio-app/gradio version 6.14.0
• Gradio Audio Cache Key Handler component
• Applications embedding the affected save_audio_to_cache function

Discovery Timeline

• 2026-06-04 - CVE-2026-10783 published to NVD
• 2026-06-04 - Last updated in NVD database

Technical Details for CVE-2026-10783

Vulnerability Analysis

The vulnerability stems from the use of a cryptographically weak hash function inside the save_audio_to_cache routine. Gradio uses this function to derive cache keys for audio assets processed through its component pipeline. A weak hash produces predictable or collision-prone outputs. An attacker operating locally with low privileges can craft inputs that collide with legitimate cache entries. This can result in cache poisoning, retrieval of unintended audio content, or limited information exposure within the application's cache directory.

The issue is categorized under CWE-327: Use of a Broken or Risky Cryptographic Algorithm. Exploitation requires local access and high complexity, narrowing realistic attack scenarios to environments where attackers already have a foothold.

Root Cause

The root cause is the selection of an outdated or weak hashing primitive for cache key derivation rather than a collision-resistant algorithm such as SHA-256. Cache key generation in save_audio_to_cache does not provide the integrity guarantees required when cached entries influence downstream processing.

Attack Vector

The attack vector is local. An authenticated local user supplies crafted audio data or filenames that collide with existing cache entries. The collision allows the attacker to overwrite or shadow cached audio assets used by legitimate Gradio sessions. The technical details are documented in the upstream GitHub Issue #13395 and the associated Pull Request #13394.

No verified proof-of-concept code is reproduced here. Refer to the VulDB entry for CVE-2026-10783 for additional context.

Detection Methods for CVE-2026-10783

Indicators of Compromise

• Unexpected entries or duplicate hash filenames within Gradio audio cache directories
• Audio output mismatches between user input and rendered results in Gradio applications
• Local processes writing to Gradio cache paths outside of expected application workflows

Detection Strategies

• Audit Gradio deployments for version 6.14.0 and inventory applications using gr.Audio components
• Monitor filesystem activity targeting the Gradio cache directory for anomalous write patterns from non-application users
• Review application logs for cache lookups returning content inconsistent with submitted inputs

Monitoring Recommendations

• Enable file integrity monitoring on Gradio cache directories on multi-user hosts
• Track installed Python package versions across development and production environments to flag vulnerable Gradio releases
• Alert on local user accounts performing repeated writes to application cache locations

How to Mitigate CVE-2026-10783

Immediate Actions Required

• Upgrade Gradio to a release that incorporates upstream patch 13394
• Restrict local access to hosts running Gradio applications, particularly multi-tenant systems
• Audit cache directory permissions to prevent cross-user write access

Patch Information

The fix is tracked as patch 13394 in the Gradio repository. Review the Pull Request #13394 for implementation details and merge into any forked or pinned versions of Gradio. Production deployments pinned to version 6.14.0 should upgrade to the patched release.

Workarounds

• Run Gradio applications under dedicated, isolated user accounts with private cache directories
• Disable or avoid the audio component in untrusted multi-user environments until the patch is applied
• Configure cache directories on filesystems with strict per-user access control lists

# Upgrade Gradio to a patched release
pip install --upgrade gradio

# Verify installed version
python -c "import gradio; print(gradio.__version__)"

# Restrict cache directory permissions (Linux example)
chmod 700 ~/.cache/gradio