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

Gradio: Audio cache key ignores metadata when saving numpy audio outputs

Low PyPI

Severity: 0.0 / 10; Low · CVSS 4.0
Exploit chance (EPSS): 0.11%; Chance of exploitation in the next 30 days. Higher than 1.09% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-327 Use of a Broken or Risky Cryptographic Algorithm
Fix: 6.15.1; Upgrade gradio to this version or later

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.

Affected versions

PyPI

Package	Vulnerable	Fixed in
gradio	`< 6.15.1`	`6.15.1`
gradio	`<= 6.14.0`	No fix yet

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

gradio PyPI → `6.15.1`

pip

pip install --upgrade "gradio>=6.15.1"

poetry

poetry add "gradio>=6.15.1"

uv

uv add "gradio>=6.15.1"

Severity breakdown

CVSS 4.0 0.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

Attack vector: Local
Attack complexity: High
Attack requirements: None
Privileges required: Low
User interaction: None
Confidentiality (vulnerable system): Low
Integrity (vulnerable system): None
Availability (vulnerable system): None
Confidentiality (subsequent systems): None
Integrity (subsequent systems): None
Availability (subsequent systems): None
Exploit maturity: Proof of concept

CVSS 3.1 2.5

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack vector: Local
Attack complexity: High
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Weakness

CWE-327: Use of a Broken or Risky Cryptographic Algorithm

The product uses a broken or risky cryptographic algorithm or protocol.

How to prevent it

Architecture and Design: When there is a need to store or transmit sensitive data, use strong, up-to-date cryptographic algorithms to encrypt that data. Select a well-vetted algorithm that is currently considered to be strong by experts in the field, and use well-tested implementations. As with all cryptographic mechanisms, the source code should be available for analysis. For example, US government systems require FIPS 140-2 certification [REF-1192]. Do not develop custom or private cryptographic algorithms. They will likely be exposed to attacks that are well-understood by cryptographers. Reverse engineering techniques are mature. If the algorithm can be compromised if attackers find out how it works, then it is especially weak. Periodically ensure that the cryptography has not become obsolete. Some older algorithms, once thought to require a billion years of computing time, can now be broken in days or hours. This includes MD4, MD5, SHA1, DES, and other algorithms that were once regarded as strong. [REF-267]
Architecture and Design: Ensure that the design allows one cryptographic algorithm to be replaced with another in the next generation or version. Where possible, use wrappers to make the interfaces uniform. This will make it easier to upgrade to stronger algorithms. With hardware, design the product at the Intellectual Property (IP) level so that one cryptographic algorithm can be replaced with another in the next generation of the hardware product.
Architecture and Design: Carefully manage and protect cryptographic keys (see CWE-320). If the keys can be guessed or stolen, then the strength of the cryptography itself is irrelevant.
Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. Industry-standard implementations will save development time and may be more likely to avoid errors that can occur during implementation of cryptographic algorithms. Consider the ESAPI Encryption feature.
Implementation, Architecture and Design: When using industry-approved techniques, use them correctly. Don't cut corners by skipping resource-intensive steps (CWE-325). These steps are often essential for preventing common attacks.

References

Advisories

Packages

github.com/gradio-app/gradio

Timeline

Jun 4, 2026 Published
Jul 23, 2026 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-j36p-7w88-g82j Gradio FileExplorer preprocess path traversal allows files outside root_dir to reach callbacks	High	Also affects gradio
GHSA-7hp7-4p35-3cx2 Gradio contains a cookie injection vulnerability	Medium	Also affects gradio
GHSA-jmh7-g254-2cq9 Gradio has SSRF via Malicious `proxy_url` Injection in `gr.load()` Config Processing	High	Also affects gradio
GHSA-pfjf-5gxr-995x Gradio has an Open Redirect in its OAuth Flow	Medium	Also affects gradio
GHSA-39mp-8hj3-5c49 Gradio is Vulnerable to Absolute Path Traversal on Windows with Python 3.13+	High	Also affects gradio
GHSA-h3h8-3v2v-rg7m Gradio: Mocked OAuth Login Exposes Server Credentials and Uses Hardcoded Session Secret	Medium	Also affects gradio
GHSA-8jw3-6x8j-v96g Gradio Allows Unauthorized File Copy via Path Manipulation	High	Also affects gradio
GHSA-wmjh-cpqj-4v6x Gradio CORS Origin Validation Bypass Vulnerability	Low	Also affects gradio

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor