# CVE-2025-5320: gradio-app gradio CORS is_valid_origin privilege escalation

> Attackers can bypass CORS restrictions in Gradio via localhost alias manipulation, potentially leading to privilege escalation.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2025
- **Updated:** 1 Jun 2025
- **Also known as:** GHSA-wmjh-cpqj-4v6x, PYSEC-2026-1423

## What is CVE-2025-5320?

CVE-2025-5320 is a medium-severity vulnerability in gradio-app gradio, published on 29 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability classified as problematic has been found in gradio-app gradio up to 5.29.1. This affects the function is_valid_origin of the component CORS Handler. The manipulation of the argument localhost_aliases leads to erweiterte Rechte. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-346 (Origin Validation Error), CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2025-5320?

3 open source packages ship an affected version, including gradio.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gradio` | PyPI | From 5.0.0 to 5.29.1 | None |
| `gradio` | PyPI | From 5.0.0 to 5.29.1 | None |
| `gradio` | PyPI | From 5.0.0 to 5.29.1 | None |

## How do I fix CVE-2025-5320?

No fix has been published for CVE-2025-5320 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-5320 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5320 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5320 and fix it if it is affected.

What it is: CVE-2025-5320 is a medium-severity vulnerability in gradio-app gradio, published on 29 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5320 exists.

Affected packages and fixed versions:
- gradio (PyPI): affected from 5.0.0 up to 5.29.1; no fix listed
- gradio (PyPI): affected from 5.0.0 up to 5.29.1; no fix listed
- gradio (PyPI): affected from 5.0.0 up to 5.29.1; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-5320/ (Markdown: https://insights.sbomify.com/CVE-2025-5320/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-5320
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-5320
- OSV: https://osv.dev/vulnerability/CVE-2025-5320

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-5320/
Summaries are generated and may contain mistakes; the official description above is the record.