Is CVE-2025-6242 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-6242 being exploited in the wild.

How severe is CVE-2025-6242?

Low severity, with a CVSS score of 3.1, published 7 July 2026.

Which products and versions are affected?

vllm (PyPI) ECOSYSTEM:introduced=0.5.0,fixed=0.11.0; Vllm 0.5.0 through 0.10.2.

Is there a fix for CVE-2025-6242?

Yes. vllm (PyPI): upgrade to 0.11.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-6242 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2025-6242?

Check whether you run vllm (PyPI) or Vllm at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-6242: PYSEC-2026-2011 - vLLM is vulnerable to Server-Side Request Forgery (SSRF) through `MediaConnector` class

CVE-2025-6242 · Severity: low · CVSS 3.1 · Published 2026-07-07

vLLM is a large language model serving framework that processes user-supplied URLs to load media content (images, audio, video) for multimodal AI models. A vulnerability in its MediaConnector class allows attackers to force the vLLM server to make requests to internal network resources, internal services, or localhost endpoints it should not access. In containerized environments, this could enable attackers to scan internal networks, disrupt other services, exfiltrate data, or trigger false scaling decisions that destabilize operations.

Technologies: vllm (PyPI), Vllm. Vendors: PyPI, Vllm.

Quick answers

Is CVE-2025-6242 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-6242 being exploited in the wild.
How severe is CVE-2025-6242?: Low severity, with a CVSS score of 3.1, published 7 July 2026.
Which products and versions are affected?: vllm (PyPI) ECOSYSTEM:introduced=0.5.0,fixed=0.11.0; Vllm 0.5.0 through 0.10.2.
Is there a fix for CVE-2025-6242?: Yes. vllm (PyPI): upgrade to 0.11.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-6242 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2025-6242?: Check whether you run vllm (PyPI) or Vllm at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

vllm (PyPI): upgrade to 0.11.0 or later
```
pip install "vllm>=0.11.0"
```

Technical details

The vulnerability is a Server-Side Request Forgery (SSRF) in the MediaConnector.load_from_url and load_from_url_async methods, which fetch media from user-provided URLs without adequate host restrictions. The vulnerable code directly processes HTTP, HTTPS, and file scheme URLs, accepting any URL the user supplies, including those pointing to internal IPs (127.0.0.1, 10.0.0.x) or localhost endpoints. An attacker requires low privileges (authenticated user) and moderate attack complexity but no user interaction. Exploitation allows access to internal services, network reconnaissance, denial of service against internal endpoints, and potential data exfiltration. The fix involves using the --allowed-media-domains option to restrict domains. The vulnerability affects vLLM versions 0.5.0 through 0.10.2, with a patch available in version 0.11.0.

Affected products

vLLM vLLM 0.5.0 through 0.10.2

Identifiers

CVE-2025-6242
GHSA-3f6c-7fw2-ppm4
PYSEC-2026-2011

Timeline

2025-10-07: disclosed
2025-10-07: patched: Fix available in version 0.11.0

References

https://github.com/vllm-project/vllm/security/advisories/GHSA-3f6c-7fw2-ppm4

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.