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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

1.1 · 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 · score source

EPSS

• CVE-2026-10783: 0.11% estimated exploitation activity in the next 30 days; percentile 1.09 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A security flaw has been discovered in gradio-app gradio 6.14.0. This affects the function saveaudiotocache 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.

Published by the source

4 Jun 2026, 00:30 UTC

Last modified by the source

14 Jul 2026, 19:56 UTC

Source last checked

26 Oct 2026, 13:46 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-6655-8ph2-63j3

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-6655-8ph2-63j3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-10783

Advisory: Gradio: Audio cache key ignores metadata when saving numpy audio outputs
IDs: CVE-2026-10783, GHSA-6655-8ph2-63j3
Record: https://patchnext.com/advisories/cve-2026-10783 (revision 3, source checked 26 Oct 2026, 13:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 1.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gradio 6.15.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI gradio: affected < 6.15.1; fixed in 6.15.1

## Suggested inspection (read-only)
- `python -m pip show gradio`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on gradio.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-6655-8ph2-63j3 (OSV record GHSA-6655-8ph2-63j3 lists affected ranges: PyPI gradio >=0 <6.15.1 (fixed))
- Verified: https://github.com/advisories/GHSA-6655-8ph2-63j3 (GitHub-reviewed advisory GHSA-6655-8ph2-63j3 lists affected ranges: PyPI gradio >=0 <6.15.1)

Commands are suggestions: review each one before running it.