CVE-2026-18621: vLLM — HIGH

A flaw was found in Data Science Pipelines (DSP). An attacker with namespace editor privileges can bypass security hardening by submitting a malicious Argo Workflow through the V1 API path. This allows the API server to create pods with elevated privileges, acting as a 'confused deputy' on behalf...

Full CISO analysis pending enrichment.

What systems are affected?

Package	Ecosystem	Vulnerable Range	Patched
vLLM	pip	—	No patch
88.6K 130 dependents Pushed yesterday 24% patched ~51d to patch Full package profile →
vLLM	pip	—	No patch
88.6K 130 dependents Pushed yesterday 24% patched ~51d to patch Full package profile →
vLLM	pip	—	No patch
88.6K 130 dependents Pushed yesterday 24% patched ~51d to patch Full package profile →
vLLM	pip	—	No patch
88.6K 130 dependents Pushed yesterday 24% patched ~51d to patch Full package profile →
vLLM	pip	—	No patch
88.6K 130 dependents Pushed yesterday 24% patched ~51d to patch Full package profile →
vLLM	pip	—	No patch
88.6K 130 dependents Pushed yesterday 24% patched ~51d to patch Full package profile →
vLLM	pip	—	No patch
88.6K 130 dependents Pushed yesterday 24% patched ~51d to patch Full package profile →
vLLM	pip	—	No patch
88.6K 130 dependents Pushed yesterday 24% patched ~51d to patch Full package profile →
vLLM	pip	—	No patch
88.6K 130 dependents Pushed yesterday 24% patched ~51d to patch Full package profile →
vLLM	pip	—	No patch
88.6K 130 dependents Pushed yesterday 24% patched ~51d to patch Full package profile →
vLLM	pip	—	No patch
88.6K 130 dependents Pushed yesterday 24% patched ~51d to patch Full package profile →
vLLM	pip	—	No patch
88.6K 130 dependents Pushed yesterday 24% patched ~51d to patch Full package profile →
vLLM	pip	—	No patch
88.6K 130 dependents Pushed yesterday 24% patched ~51d to patch Full package profile →
rhoai/odh-ml-pipelines-api-server-v2-rhel9	—	—	No patch

How severe is it?

CVSS 3.1

7.6 / 10

EPSS

N/A

Exploitation Status

No known exploitation

Sophistication

N/A

What is the attack surface?

AV Network

AC Low

PR Low

UI None

S Unchanged

C High

I Low

A Low

What should I do?

No patch available

Monitor for updates. Consider compensating controls or temporary mitigations.

Which compliance frameworks are affected?

Compliance analysis pending. Sign in for full compliance mapping when available.

Frequently Asked Questions

What is CVE-2026-18621?

A flaw was found in Data Science Pipelines (DSP). An attacker with namespace editor privileges can bypass security hardening by submitting a malicious Argo Workflow through the V1 API path. This allows the API server to create pods with elevated privileges, acting as a 'confused deputy' on behalf of the attacker. Successful exploitation grants the attacker node-root access, enabling arbitrary code execution and full control over the underlying node.

Is CVE-2026-18621 actively exploited?

No confirmed active exploitation of CVE-2026-18621 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-18621?

No patch is currently available. Monitor vendor advisories for updates.

What is the CVSS score for CVE-2026-18621?

CVE-2026-18621 has a CVSS v3.1 base score of 7.6 (HIGH).

What are the technical details?

Original Advisory

A flaw was found in Data Science Pipelines (DSP). An attacker with namespace editor privileges can bypass security hardening by submitting a malicious Argo Workflow through the V1 API path. This allows the API server to create pods with elevated privileges, acting as a 'confused deputy' on behalf of the attacker. Successful exploitation grants the attacker node-root access, enabling arbitrary code execution and full control over the underlying node.

Weaknesses (CWE)

CWE-266 Incorrect Privilege Assignment

CWE-266 — Incorrect Privilege Assignment: A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.

[Architecture and Design, Operation] Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
[Architecture and Design, Operation] Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.

Source: MITRE CWE corpus.