Node-root code execution via unchecked V1 workflows
Published Aug 10, 2026 · Updated Aug 10, 2026
Privilege escalation in Red Hat Data Science Pipelines allows remote authenticated users to gain node-root access through the V1 API. The V1 Argo template path accepts an attacker-supplied Workflow spec without the v2 compiler's hardening, so the API server creates a privileged pod as a confused deputy. Namespace editor privileges and a namespace with GPU operators or anyuid or privileged SCCs are required; successful exploitation permits arbitrary code execution and control of the underlying node.
Summary
What happened
Privilege escalation in Red Hat Data Science Pipelines allows remote authenticated users to gain node-root access through the V1 API. The V1 Argo template path accepts an attacker-supplied Workflow spec without the v2 compiler's hardening, so the API server creates a privileged pod as a confused deputy. Namespace editor privileges and a namespace with GPU operators or anyuid or privileged SCCs are required; successful exploitation permits arbitrary code execution and control of the underlying node.
The record
- CVE
- CVE-2026-18621
- Published
- Aug 10, 2026
- Updated
- Aug 10, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-266, T1610, T1611
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 10, 2026CVE publishedPublication date reported by the CVE source.
- Aug 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo