Is there a patch available for CVE-2026-10783?

Yes, a patch is available for CVE-2026-10783. Update the affected software to the latest version immediately.

Gradio CVE-2026-10783

Q: What is the CVSS score of CVE-2026-10783?

CVE-2026-10783 has a CVSS 4.0 base score of 1.1 (Low). CVSS vector: 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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

EUVD-2026-34187 LOW

Use of a Broken or Risky Cryptographic Algorithm (CWE-327)

2026-06-04 cna@vuldb.com

GHSA-6655-8ph2-63j3

Information Disclosure Gradio

1.1

CVSS 4.0 · Vendor: vuldb

Severity by source

Vendor (vuldb) PRIMARY

1.1 LOW

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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from Vendor (vuldb) · only source for this CVE.

CVSS VectorVendor: vuldb

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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack Vector

Local

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Source Code Evidence Fetched

Jun 04, 2026 - 00:26 vuln.today

Analysis Generated

Jun 04, 2026 - 00:26 vuln.today

DescriptionCVE.org

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.

AnalysisAI

Cache key collision in Gradio 6.14.0's audio processing component allows a local low-privileged attacker to trigger information disclosure by exploiting incomplete hash inputs in the save_audio_to_cache function. Two audio arrays with identical raw bytes but differing metadata (sample rate, format, dtype, or shape) resolve to the same cache directory path, causing one cached audio file to overwrite or be served in place of another. Publicly available exploit code exists per the CVSS 4.0 E:P modifier and CVE description, though no active exploitation has been confirmed via CISA KEV. The CVSS 4.0 score of 1.1 accurately reflects the narrow real-world impact given the mandatory local access and high attack complexity.

Technical ContextAI

The vulnerability resides in gradio/processing_utils.py within the save_audio_to_cache function. Prior to fix PR #13394, cache directory paths were derived exclusively from hash_bytes(data.tobytes()) - hashing only the raw PCM byte content of the numpy audio array. Because the hash excluded metadata such as sample rate, format string, data type (e.g., int16 vs uint16), and array shape (mono vs stereo), two semantically distinct audio files with coincidentally identical raw bytes would hash to the same cache key. CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) identifies the root cause class: the legacy hash function is cryptographically insufficient for its purpose as a unique cache discriminator. The fix in PR #13394 replaces this with SHA-256 over a JSON-serialized metadata envelope (cache_schema, dtype, format, sample_rate, shape) concatenated with the raw audio bytes, eliminating the collision vector entirely.

RemediationAI

Apply the upstream fix from GitHub pull request #13394 (https://github.com/gradio-app/gradio/pull/13394), which replaces the incomplete hash with SHA-256 over a full metadata envelope. A specific patched release version was not confirmed in the provided intelligence beyond the changeset designation; monitor the official Gradio releases at https://github.com/gradio-app/gradio/ for the release incorporating this changeset. As a compensating control prior to patching, restrict local system access to the Gradio host so that only trusted users can interact with the application - this directly addresses the AV:L prerequisite. Disabling audio caching at the application level, if the feature is configurable, would also eliminate the collision surface entirely. Network-layer controls provide no mitigation benefit given the local-only attack vector.