# CVE-2026-48545: Gradio < 6.15.0 Cookie Injection via Shared Proxy Client

> Attackers can inject cookies via a shared HTTP client to hijack sessions across multiple Gradio Spaces, requiring an upgrade to fix.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 May 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-7hp7-4p35-3cx2, PYSEC-2026-2178

## What is CVE-2026-48545?

CVE-2026-48545 is a high-severity vulnerability in Gradio Project Gradio, published on 27 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Gradio before version 6.15.0 contains a cookie injection vulnerability that allows remote attackers to perform cross-Space session fixation by exploiting a shared module-level HTTP client used across all users in the reverse proxy endpoint. Attackers controlling any HF Space can return a parent-domain cookie that the shared client stores and automatically replays into all subsequent proxy requests to other legitimate Spaces, affecting all users of the same Gradio deployment.

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2026-48545?

3 open source packages ship an affected version, including gradio. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gradio` | PyPI | All versions | 6.15.0 |
| `gradio` | PyPI | All versions | 6.15.0 |
| `gradio` | PyPI | All versions | 6.15.0 |

Products: Gradio Project Gradio.

## How do I fix CVE-2026-48545?

Upgrade gradio to 6.15.0 or later.

## Is CVE-2026-48545 being exploited?

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

## Other vulnerabilities in Gradio Project Gradio

- [CVE-2024-39236](https://insights.sbomify.com/CVE-2024-39236/): Withdrawn Advisory: Gradio was discovered to contain a code injection vulnerability via the component /gradio/component_meta.py (critical 9.8)
- [CVE-2023-6572](https://insights.sbomify.com/CVE-2023-6572/): Command Injection in gradio-app/gradio (critical 9.6)
- [CVE-2022-24770](https://insights.sbomify.com/CVE-2022-24770/): Improper Neutralization of Formula Elements in a CSV File in Gradio Flagging (high 8.8)
- [CVE-2026-49119](https://insights.sbomify.com/CVE-2026-49119/): Gradio < 6.16.0 Path Traversal via FileExplorer.preprocess() (high 8.7)
- [CVE-2025-23042](https://insights.sbomify.com/CVE-2025-23042/): Gradio Blocked Path ACL Bypass Vulnerability (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48545 and fix it if it is affected.

What it is: CVE-2026-48545 is a high-severity vulnerability in Gradio Project Gradio, published on 27 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48545 exists.

Affected packages and fixed versions:
- gradio (PyPI): affected all versions; fixed in 6.15.0
- gradio (PyPI): affected all versions; fixed in 6.15.0
- gradio (PyPI): affected all versions; fixed in 6.15.0

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-2026-48545/ (Markdown: https://insights.sbomify.com/CVE-2026-48545/index.md)
```

## Sources

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

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