CVE-2026-115915 Vulnerability Analysis & Exploit Details

CVE-2026-115915
Vulnerability Scoring

8.1
/10
Severe Risk

Cybersecurity professionals consider CVE-2026-115915 an immediate threat requiring urgent mitigation.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-115915 Details

Status: Analyzed

Last updated: 🕞 28 Oct 2026, 15:37 UTC
Originally published on: 🕕 26 Oct 2026, 18:17 UTC

Time between publication and last update: 1 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

CVE-2026-115915 Vulnerability Summary

CVE-2026-115915: vLLM is an inference and serving engine for large language models. Prior to 0.32.0, ImageMediaIO passes attacker-controlled image bytes to Pillow through Image.open(BytesIO(data)) without restricting decoder selection, and the MIME label does not constrain the selected format. Image-capable request paths through parse_image() and fetch_image() can therefore dispatch an EPS payload to host components. A host with Ghostscript affected by CVE-2024-29510 can execute commands with the vLLM process's privileges, while environments using Pillow 12.0.0 through 12.2.0 can trigger CVE-2026-59203 and exhaust media-loading workers. Deployments without the applicable vulnerable dependency are not affected by that corresponding impact. This issue is fixed in version 0.32.0.

Assessing the Risk of CVE-2026-115915

Access Complexity Graph

The exploitability of CVE-2026-115915 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-115915

CVE-2026-115915 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-115915, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-115915, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-115915 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2026-115915 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2026-115915 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-115915 References

External References

CWE Common Weakness Enumeration

CWE-183

CAPEC Common Attack Pattern Enumeration and Classification

  • Double Encoding CAPEC-120 The adversary utilizes a repeating of the encoding process for a set of characters (that is, character encoding a character encoding of a character) to obfuscate the payload of a particular request. This may allow the adversary to bypass filters that attempt to detect illegal characters or strings, such as those that might be used in traversal or injection attacks. Filters may be able to catch illegal encoded strings, but may not catch doubly encoded strings. For example, a dot (.), often used in path traversal attacks and therefore often blocked by filters, could be URL encoded as %2E. However, many filters recognize this encoding and would still block the request. In a double encoding, the % in the above URL encoding would be encoded again as %25, resulting in %252E which some filters might not catch, but which could still be interpreted as a dot (.) by interpreters on the target.
  • Using Leading 'Ghost' Character Sequences to Bypass Input Filters CAPEC-3 Some APIs will strip certain leading characters from a string of parameters. An adversary can intentionally introduce leading "ghost" characters (extra characters that don't affect the validity of the request at the API layer) that enable the input to pass the filters and therefore process the adversary's input. This occurs when the targeted API will accept input data in several syntactic forms and interpret it in the equivalent semantic way, while the filter does not take into account the full spectrum of the syntactic forms acceptable to the targeted API.
  • Exploiting Multiple Input Interpretation Layers CAPEC-43 An attacker supplies the target software with input data that contains sequences of special characters designed to bypass input validation logic. This exploit relies on the target making multiples passes over the input data and processing a "layer" of special characters with each pass. In this manner, the attacker can disguise input that would otherwise be rejected as invalid by concealing it with layers of special/escape characters that are stripped off by subsequent processing steps. The goal is to first discover cases where the input validation layer executes before one or more parsing layers. That is, user input may go through the following logic in an application: <parser1> --> <input validator> --> <parser2>. In such cases, the attacker will need to provide input that will pass through the input validator, but after passing through parser2, will be converted into something that the input validator was supposed to stop.
  • Using Unicode Encoding to Bypass Validation Logic CAPEC-71 An attacker may provide a Unicode string to a system component that is not Unicode aware and use that to circumvent the filter or cause the classifying mechanism to fail to properly understanding the request. That may allow the attacker to slip malicious data past the content filter and/or possibly cause the application to route the request incorrectly.

Vulnerable Configurations

  • cpe:2.3:a:vllm:vllm:0.30.0:-:*:*:*:*:*:*
    cpe:2.3:a:vllm:vllm:0.30.0:-:*:*:*:*:*:*
  • cpe:2.3:a:vllm:vllm:0.30.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:vllm:vllm:0.30.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:vllm:vllm:0.30.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:vllm:vllm:0.30.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:vllm:vllm:0.30.1:rc0:*:*:*:*:*:*
    cpe:2.3:a:vllm:vllm:0.30.1:rc0:*:*:*:*:*:*
  • cpe:2.3:a:vllm:vllm:0.31.0:-:*:*:*:*:*:*
    cpe:2.3:a:vllm:vllm:0.31.0:-:*:*:*:*:*:*
  • cpe:2.3:a:vllm:vllm:0.31.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:vllm:vllm:0.31.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:vllm:vllm:0.31.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:vllm:vllm:0.31.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:vllm:vllm:0.31.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:vllm:vllm:0.31.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:vllm:vllm:0.31.0:rc4:*:*:*:*:*:*
    cpe:2.3:a:vllm:vllm:0.31.0:rc4:*:*:*:*:*:*
  • cpe:2.3:a:vllm:vllm:0.31.0:rc5:*:*:*:*:*:*
    cpe:2.3:a:vllm:vllm:0.31.0:rc5:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-115915: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-93011 – A flaw was found in dnsmasq. After a reduction of internal domain-name buffer sizes, the DNSSEC validator can write a few bytes past a name buffer ...
  • CVE-2026-93008 – A flaw was found in dnsmasq. When following a CNAME in a DNS response, the resolver can cache records for the CNAME target without checking that th...
  • CVE-2026-93007 – A flaw was found in dnsmasq. The TCP DNS service uses a small fixed pool of child processes and does not set a receive timeout on client connection...
  • CVE-2026-93006 – A flaw was found in dnsmasq. The TFTP server can serve the wrong file contents because a recently used transfer cache is not invalidated when a tra...
  • CVE-2026-56056 – Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Mamunur Rashid The Post Grid the-post-grid al...