# CVE-2026-34753: vLLM affected by Server-Side Request Forgery (SSRF) in `download_bytes_from_url `

> Attackers can force the vLLM server to make arbitrary HTTP requests, potentially accessing internal services or cloud metadata endpoints.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-pf3h-qjgv-vcpr, PYSEC-2026-3410

## What is CVE-2026-34753?

CVE-2026-34753 is a medium-severity server-side request forgery vulnerability in Vllm Vllm, published on 6 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

vLLM is an inference and serving engine for large language models (LLMs). From 0.16.0 to before 0.19.0, a server-side request forgery (SSRF) vulnerability in download_bytes_from_url allows any actor who can control batch input JSON to make the vLLM batch runner issue arbitrary HTTP/HTTPS requests from the server, without any URL validation or domain restrictions.
This can be used to target internal services (e.g. cloud metadata endpoints or internal HTTP APIs) reachable from the vLLM host. This vulnerability is fixed in 0.19.0.

Weakness: CWE-918 (Server-Side Request Forgery)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vllm` | PyPI | From 0.16.0 | 0.19.0 |
| `vllm` | PyPI | From 0.16.0 | 0.19.0 |
| `vllm` | PyPI | From 0.16.0 | 0.19.0 |

Products: Vllm Vllm.

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

Upgrade vllm to 0.19.0 or later.

## Is CVE-2026-34753 being exploited?

There is no known exploitation of CVE-2026-34753 in the wild and no public exploit code.

Public exploit code:

- https://github.com/Dhiaelhak-Rached/CVE-2026-34753 (github_poc): https://github.com/Dhiaelhak-Rached/CVE-2026-34753

## Other vulnerabilities in Vllm Vllm

- [CVE-2025-32444](https://insights.sbomify.com/CVE-2025-32444/): vLLM Vulnerable to Remote Code Execution via Mooncake Integration (critical 10.0)
- [CVE-2026-22778](https://insights.sbomify.com/CVE-2026-22778/): vLLM leaks a heap address when PIL throws an error (critical 9.8)
- [CVE-2025-47277](https://insights.sbomify.com/CVE-2025-47277/): vLLM Allows Remote Code Execution via PyNcclPipe Communication Service (critical 9.8)
- [CVE-2024-11041](https://insights.sbomify.com/CVE-2024-11041/): Remote Code Execution in vllm-project/vllm (critical 9.8)
- [CVE-2026-48746](https://insights.sbomify.com/CVE-2026-48746/): vLLM: OpenAI auth bypass (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34753 is a medium-severity server-side request forgery vulnerability in Vllm Vllm, published on 6 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-34753 in the wild and no public exploit code.

Affected packages and fixed versions:
- vllm (PyPI): affected from 0.16.0; fixed in 0.19.0
- vllm (PyPI): affected from 0.16.0; fixed in 0.19.0
- vllm (PyPI): affected from 0.16.0; fixed in 0.19.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-34753/ (Markdown: https://insights.sbomify.com/CVE-2026-34753/index.md)
```

## Sources

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

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