Quick answers
- Is CVE-2026-24779 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-24779 being exploited in the wild.
- How severe is CVE-2026-24779?
- High severity, with a CVSS score of 7.1, published 27 January 2026.
- Which products and versions are affected?
- vllm (PyPI) ECOSYSTEM:introduced=0,fixed=0.14.1; Red Hat AI Inference Server 3.2, 3.3.
- Is there a fix for CVE-2026-24779?
- Yes. vllm (PyPI): upgrade to 0.14.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-24779 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-24779?
- Check whether you run vllm (PyPI), Red Hat AI Inference Server 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.14.1 or later
pip install "vllm>=0.14.1"
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in the MediaConnector.load_from_url and load_from_url_async methods of vLLM. The vulnerability stems from a differential in how backslashes (\) are handled by Python's urllib.parse (used for validation) and urllib3 (used by the requests library to fetch the content). An attacker with low privileges can provide a crafted URL that passes the hostname allowlist check in urllib but resolves to an internal or restricted IP address when fetched by requests. This allows for internal network scanning, interaction with private metadata endpoints, or unauthorized access to other internal services. The issue is fixed in version 0.14.1.
Affected products
- vLLM Project vLLM < 0.14.1
Identifiers
- CVE-2026-24779
- GHSA-qh4c-xf7m-gxfc
- PYSEC-2026-2020
Timeline
- 2026-01-27: disclosed
- 2026-01-28: advisory: GitHub Advisory published