CVE-2026-24779: Vllm VLLM Vulnerable To Server-Side Request Vulnerability

HIGH
Advisory Identifier: GHSA-qh4c-xf7m-gxfc
CVSS 7.1
CWE-918
Published
Advisory Summary

CVE-2026-24779 is a HIGH (CVSS 7.1) vllm vulnerable to server-side request vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting Vllm libraries in the PyPI ecosystem. The issue involves vllm vulnerable to server-side request forgery (ssrf) through mediaconnector. Remediation is available by upgrading affected packages to version 0.14.1.

CVE-2026-24779 at a Glance

CVE Identifier CVE-2026-24779
GHSA Identifier GHSA-qh4c-xf7m-gxfc
Severity HIGH
CVSS v3.1 Base Score 7.1
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product Vllm
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 7.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability Low (A:L)

How to Fix CVE-2026-24779

To remediate this vulnerability, upgrade all affected Vllm dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

vllm fixed: 0.14.1
pip install vllm>=0.14.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show vllm

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-24779, inspect your installed packages using pip:

pip show vllm

Analyze the terminal output to locate any version of Vllm in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.14.1), your application is affected.

Note: The pip show vllm command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In Vllm, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary A Server-Side Request Forgery (SSRF) vulnerability exists in the `MediaConnector` class within the vLLM project's multimodal feature set. The load_from_url and load_from_url_async methods obtain and process media from URLs provided by users, using different Python parsing libraries when restricting the target host. These two parsing libraries have different interpretations of backslashes, which allows the host name restriction to be bypassed. This allows an attacker to coerce the vLLM server into making arbitrary requests to internal network resources. This vulnerability is particularly critical in containerized environments like `llm-d`, where a compromised vLLM pod could be used to scan the internal network, interact with other pods, and potentially cause Denial of Service or access sensitive data. For example, an attacker could make the vLLM pod send malicious requests to an internal `llm-d` management endpoint, leading to system instability by falsely reporting metrics like the KV cache state. ### Details The core of the vulnerability lies in the `MediaConnector.load_from_url` method and its asynchronous counterpart. These methods accept a URL string to fetch media content (images, audio, video). > def load_from_url( > self, > url: str, > media_io: MediaIO[_M], > *, > fetch_timeout: int | None = None, > ) -> _M: # type: ignore[type-var] > url_spec = urlparse(url) > > if url_spec.scheme.startswith("http"): > self._assert_url_in_allowed_media_domains(url_spec) > > connection = self.connection > data = connection.get_bytes( > url, > timeout=fetch_timeout, > allow_redirects=envs.VLLM_MEDIA_URL_ALLOW_REDIRECTS, > ) > > return media_io.load_bytes(data) The URL validation uses the `urlparse` function from Python's `urllib` module, while the request is made using the `request` function from Python's `requests` module. The `requests` module's underlying URL parsing is implemented using the `parse_url` function from Python's `urllib3`. These two parsing functions follow different URL specifications; one is implemented according to the RFC 3986 specification, and the other is implemented according to the WHATWG Living Standard. There is a difference in how the two functions handle backslashes (`\`) in URLs, which allows the hostname restriction to be bypassed. ### Fix * https://github.com/vllm-project/vllm/pull/32746

CVE-2026-24779 Affected Vllm Versions

1 component(s)
Fixed Versions:
0.14.1
Product / Package Ecosystem Affected Versions Fixed Version
vllm
PyPI
< 0.14.1
0.14.1

References

GitHub Advisory / Wiki ADVISORY
https://github.com/vllm-project/vllm/security/advisories/GHSA-qh4c-xf7m-gxfc
NVD — CVE-2026-24779 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-24779
Vllm Source Repository REPOSITORY
https://github.com/vllm-project/vllm/pull/32746
Security Fix Commit FIX COMMIT
https://github.com/vllm-project/vllm/commit/f46d576c54fb8aeec5fc70560e850bed38ef17d7
Vllm Security Information SECURITY
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-24779.json
pypi.org/project/vllm WEB
https://pypi.org/project/vllm
Vllm Source Repository REPOSITORY
https://github.com/vllm-project/vllm
Vllm Source Repository REPOSITORY
https://github.com/pypa/advisory-database/tree/main/vulns/vllm/PYSEC-2026-2020.yaml
GitHub Advisory / Wiki ADVISORY
https://github.com/advisories/GHSA-qh4c-xf7m-gxfc
bugzilla.redhat.com/show_bug.cgi WEB
https://bugzilla.redhat.com/show_bug.cgi?id=2433624
Vllm Security Information SECURITY
https://access.redhat.com/security/cve/CVE-2026-24779
access.redhat.com/errata/rhsa-2026:42... WEB
https://access.redhat.com/errata/RHSA-2026:42644
access.redhat.com/errata/rhsa-2026:37... WEB
https://access.redhat.com/errata/RHSA-2026:3782
access.redhat.com/errata/rhsa-2026:34... WEB
https://access.redhat.com/errata/RHSA-2026:3462
access.redhat.com/errata/rhsa-2026:34... WEB
https://access.redhat.com/errata/RHSA-2026:3461
access.redhat.com/errata/rhsa-2026:30... WEB
https://access.redhat.com/errata/RHSA-2026:30089
access.redhat.com/errata/rhsa-2026:30... WEB
https://access.redhat.com/errata/RHSA-2026:30088
access.redhat.com/errata/rhsa-2026:30... WEB
https://access.redhat.com/errata/RHSA-2026:30087
access.redhat.com/errata/rhsa-2026:19... WEB
https://access.redhat.com/errata/RHSA-2026:19712
access.redhat.com/errata/rhsa-2026:10... WEB
https://access.redhat.com/errata/RHSA-2026:10184

Frequently Asked Questions

What is CVE-2026-24779?
CVE-2026-24779 is a security vulnerability in Vllm involving vLLM vulnerable to Server-Side Request Forgery (SSRF) through MediaConnector under CWE-918: Server-Side Request Forgery (SSRF).
Which Vllm versions are affected?
Affected versions include releases prior to 0.14.1 across affected packages: vllm.
What version fixes CVE-2026-24779?
Upgrading to 0.14.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is vllm affected?
Yes, vllm is affected in releases prior to 0.14.1. Upgrade your dependency to 0.14.1 or later.
What is the CVSS score of CVE-2026-24779?
CVE-2026-24779 has a CVSS v3.1 base score of 7.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L.
What CWE is associated with CVE-2026-24779?
CVE-2026-24779 is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check PyPI dependencies for CVE-2026-24779?
Run the dependency tree command: 'pip show vllm'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-qh4c-xf7m-gxfc",
  "modified" : "2026-07-21T12:32:16Z",
  "published" : "2026-01-28T16:14:28Z",
  "aliases" : [ "CVE-2026-24779" ],
  "summary" : "vLLM vulnerable to Server-Side Request Forgery (SSRF) through MediaConnector",
  "details" : "### Summary\nA Server-Side Request Forgery (SSRF) vulnerability exists in the `MediaConnector` class within the vLLM project's multimodal feature set. The load_from_url and load_from_url_async methods obtain and process media from URLs provided by users, using different Python parsing libraries when restricting the target host. These two parsing libraries have different interpretations of backslashes, which allows the host name restriction to be bypassed. This allows an attacker to coerce the vLLM server into making arbitrary requests to internal network resources.\n\nThis vulnerability is particularly critical in containerized environments like `llm-d`, where a compromised vLLM pod could be used to scan the internal network, interact with other pods, and potentially cause Denial of Service or access sensitive data. For example, an attacker could make the vLLM pod send malicious requests to an internal `llm-d` management endpoint, leading to system instability by falsely reporting metrics like the KV cache state.\n\n### Details\nThe core of the vulnerability lies in the `MediaConnector.load_from_url` method and its asynchronous counterpart. These methods accept a URL string to fetch media content (images, audio, video).\n\n>     def load_from_url(\n>         self,\n>         url: str,\n>         media_io: MediaIO[_M],\n>         *,\n>         fetch_timeout: int | None = None,\n>     ) -> _M:  # type: ignore[type-var]\n>         url_spec = urlparse(url)\n> \n>         if url_spec.scheme.startswith(\"http\"):\n>             self._assert_url_in_allowed_media_domains(url_spec)\n> \n>             connection = self.connection\n>             data = connection.get_bytes(\n>                 url,\n>                 timeout=fetch_timeout,\n>                 allow_redirects=envs.VLLM_MEDIA_URL_ALLOW_REDIRECTS,\n>             )\n> \n>             return media_io.load_bytes(data)\n\nThe URL validation uses the `urlparse` function from Python's `urllib` module, while the request is made using the `request` function from Python's `requests` module. The `requests` module's underlying URL parsing is implemented using the `parse_url` function from Python's `urllib3`. These two parsing functions follow different URL specifications; one is implemented according to the RFC 3986 specification, and the other is implemented according to the WHATWG Living Standard. There is a difference in how the two functions handle backslashes (`\\`) in URLs, which allows the hostname restriction to be bypassed.\n\n### Fix\n\n* https://github.com/vllm-project/vllm/pull/32746",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "vllm"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.14.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/vllm-project/vllm/security/advisories/GHSA-qh4c-xf7m-gxfc"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-24779"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/vllm-project/vllm/pull/32746"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/vllm-project/vllm/commit/f46d576c54fb8aeec5fc70560e850bed38ef17d7"
  }, {
    "type" : "WEB",
    "url" : "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-24779.json"
  }, {
    "type" : "WEB",
    "url" : "https://pypi.org/project/vllm"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/vllm-project/vllm"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pypa/advisory-database/tree/main/vulns/vllm/PYSEC-2026-2020.yaml"
  }, {
    "type" : "ADVISORY",
    "url" : "https://github.com/advisories/GHSA-qh4c-xf7m-gxfc"
  }, {
    "type" : "WEB",
    "url" : "https://bugzilla.redhat.com/show_bug.cgi?id=2433624"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/security/cve/CVE-2026-24779"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:42644"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:3782"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:3462"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:3461"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:30089"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:30088"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:30087"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:19712"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:10184"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-01-28T16:14:28Z",
    "nvd_published_at" : "2026-01-27T22:15:57Z"
  }
}