BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-31892High confidence

WorkflowTemplate Security Bypass via podSpecPatch in Strict/Secure Reference Mode

argoproj · argo-workflows

Official source article: GitHub GHSA-3WF5-G532-RCRR ↗. Check the applicable product and release in the original source.

8.9HighCVSS 4.0
Recommended action
Within 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Critical, raised one band.upgradedsince 15 Jul 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • EPSS is 0.65% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs argoproj argo-workflows and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Open-source package ranges6 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Gogithub.com/argoproj/argo-workflowsSEMVER: introduced 2.9.0Not statedOSV record ↗aggregator derived · 10 Sep 2026
Gogithub.com/argoproj/argo-workflows/v3SEMVER: introduced 0; fixed 3.7.113.7.11OSV record ↗aggregator derived · 10 Sep 2026
Gogithub.com/argoproj/argo-workflows/v4SEMVER: introduced 0; fixed 4.0.24.0.2OSV record ↗aggregator derived · 10 Sep 2026
gogithub.com/argoproj/argo-workflows>= 2.9.0, < 3.0.0Not statedGitHub advisory ↗upstream repository advisory · 11 Mar 2026
gogithub.com/argoproj/argo-workflows/v3< 3.7.113.7.11GitHub advisory ↗upstream repository advisory · 11 Mar 2026
gogithub.com/argoproj/argo-workflows/v4< 4.0.24.0.2GitHub advisory ↗upstream repository advisory · 11 Mar 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-31892 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitygithub.com/argoproj/argo-workflows: Argo Workflows: Security bypass allows privilege escalation via podSpecPatch field
21 fixed

The vendor explicitly identifies these products or versions as containing the fix.

  • registry.redhat.io/rhoai/odh-data-science-pipelines-argo-argoexec-rhel9@sha256:3c8b56f1d7e2084a93dd6ea951e4328bb969fa3443452790db10a9a01bead27b_ppc64le as a component of Red Hat OpenShift AI 2.25
  • registry.redhat.io/rhoai/odh-data-science-pipelines-argo-argoexec-rhel9@sha256:c7b7f0e7a0864676517e56b9fd75d2ce85b152708842b83f74720519490a4b36_arm64 as a component of Red Hat OpenShift AI 2.25
  • registry.redhat.io/rhoai/odh-data-science-pipelines-argo-argoexec-rhel9@sha256:ffdfd1b2f082296677737ea1a585cd29016beaa72a8c88b67bc74e114624eb92_amd64 as a component of Red Hat OpenShift AI 2.25
  • registry.redhat.io/rhoai/odh-data-science-pipelines-argo-workflowcontroller-rhel9@sha256:72f4630626f2089823c9a9c413b5bad245e63a7569468581804e34790fd3941e_ppc64le as a component of Red Hat OpenShift AI 2.25
  • registry.redhat.io/rhoai/odh-data-science-pipelines-argo-workflowcontroller-rhel9@sha256:acaba51bd115f189ba1f818c1bf141df0907bb354e2639a4aa4dad3ff7c68335_amd64 as a component of Red Hat OpenShift AI 2.25
  • registry.redhat.io/rhoai/odh-data-science-pipelines-argo-workflowcontroller-rhel9@sha256:e4214f06d7770398ee48065b1381528bc55084f193a35e10ff0def2f56967f71_arm64 as a component of Red Hat OpenShift AI 2.25
  • registry.redhat.io/rhoai/odh-ml-pipelines-api-server-v2-rhel9@sha256:1cb63738914fd92687e1268e643d8a082e8b7126429c9b42433d9b32084c21b5_ppc64le as a component of Red Hat OpenShift AI 2.25
  • registry.redhat.io/rhoai/odh-ml-pipelines-api-server-v2-rhel9@sha256:49d113de4250fb5f96387047052a11979fb410cefb03cfe84025a1bdc3cc2130_amd64 as a component of Red Hat OpenShift AI 2.25
  • registry.redhat.io/rhoai/odh-ml-pipelines-api-server-v2-rhel9@sha256:8aafa4099d297bab85c6e38ce443ab9ea6f895d97839ca956d641574dce85209_arm64 as a component of Red Hat OpenShift AI 2.25
  • registry.redhat.io/rhoai/odh-ml-pipelines-driver-rhel9@sha256:256a1a514bed575d0fda9b97f5ec28b651dbe6a5a7c0992eae8e0ee4811eb483_arm64 as a component of Red Hat OpenShift AI 2.25
  • registry.redhat.io/rhoai/odh-ml-pipelines-driver-rhel9@sha256:71ee1e02f693d94555fc28956c20cc28817768c3242c628c3705604dcf8d63df_ppc64le as a component of Red Hat OpenShift AI 2.25
  • registry.redhat.io/rhoai/odh-ml-pipelines-driver-rhel9@sha256:c8bfa95bd3076931e351a7abcee4b1efc31bd42eb3d41d205b31c4101eb021a2_amd64 as a component of Red Hat OpenShift AI 2.25
Summary
A flaw was found in Argo Workflows. A user with privileges to submit workflows can bypass security settings defined in a WorkflowTemplate by including a `podSpecPatch` field in their workflow submission. This allows them to circumvent restrictions, even when `templateReferencing: Strict` is configured, potentially leading to unauthorized resource access or privilege escalation.
Remediation
For Red Hat OpenShift AI 2.25.5 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.redhat.com/en/documentation/red_hat_openshift_ai/
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-11206

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. From 2.9.0 to before 4.0.2 and 3.7.11, A user who can submit Workflows can completely bypass all security settings defined in a WorkflowTemplate by including a podSpecPatch field in their Workflow submission. This works even when the controller is configured with templateReferencing: Strict, which is specifically documented as a mechanism to restrict users to admin-approved templates. The podSpecPatch field on a submitted Workflow takes precedence over the referenced WorkflowTemplate during spec merging and is applied directly to the pod spec at creation time with no security validation. This vulnerability is fixed in 4.0.2 and 3.7.11.

What

Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. From 2.9.0 to before 4.0.2 and 3.7.11, A user who can submit Workflows can completely bypass all security settings defined in a WorkflowTemplate by including a podSpecPatch field in their Workflow submission. This works even when the controller is configured with templateReferencing: Strict, which is specifically documented as a mechanism to restrict users to admin-approved templates. The podSpecPatch field on a submitted Workflow takes precedence over the referenced WorkflowTemplate during spec merging and is applied directly to the pod spec at creation time with no security validation. This vulnerability is fixed in 4.0.2 and 3.7.11.

Why

The application performs an authorisation check, but it does not correctly enforce the required permission boundary.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. From 2.9.0 to before 4.0.2 and 3.7.11, A user who can submit Workflows can completely bypass all security settings defined in a WorkflowTemplate by including a podSpecPatch field in their Workflow submission. This works even when the controller is configured with templateReferencing: Strict, which is specifically documented as a mechanism to restrict users to admin-approved templates. The podSpecPatch field on a submitted Workflow takes precedence over the referenced WorkflowTemplate during spec merging and is applied directly to the pod spec at creation time with no security validation. This vulnerability is fixed in 4.0.2 and 3.7.11.

Why

The application performs an authorisation check, but it does not correctly enforce the required permission boundary.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Incorrect Authorization → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-863 ↗

CWE-863: Incorrect Authorization. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:H

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCHighSubsequent-system confidentiality: A successful attack can cause a major loss.SIHighSubsequent-system integrity: A successful attack can cause a major loss.SAHighSubsequent-system availability: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkCWE-863Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

JVN iPedia · Japanese · JVNDB-2026-026195Argo Project AuthorsのArgo Workflowsにおけるアクセス制御に関する脆弱性

Argo Workflowsは、Kubernetes上で並列ジョブをオーケストレーションするためのオープンソースのコンテナネイティブワークフローエンジンです。バージョン3.7.15および4.0.6以前では、CVE-2026-31892のallow-list（許可リスト）修正が不完全でした。これはworkflow/util/merge.goのValidateUserOverridesおよびSanitizeUserWorkflowSpecがWorkflowSpecのトップレベルフィールドのみをリフレクションを使って検査し、WorkflowSpec.ArtifactGCが丸ごと許可リストに含まれていたためです。このフィールドの背後にある構造体WorkflowLevelArtifactGCにはPodSpecPatchサブフィールドがあり、その内容はartifact-GCポッド上のutil.ApplyPodSpecPatchに修正されずに渡されます。これは元の修正でWorkflowSpec.PodSpecPatchに対して対策が取られたのと同じ問題です。そのため、templateReferencingをStrictまたはSecureに設定し（出力アーティファクトを宣言する参照されるWorkflowTemplateに対して）、spec.artifactGC.strategyがOnWorkflowCompletionに設定されているワークフローをユーザーが送信すると、artifact-GCポッドに任意の戦略的マージパッチを注入できてしまいます。これにはhostPathボリューム、privileged:true、任意のイメージとコマンド、hostNetwork:trueが含まれており、Strict/Secure参照モードの目的が失われます。この問題はバージョン3.7.15および4.0.6で修正されています。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-015912Argo Project AuthorsのArgo Workflowsにおける不正な認証に関する脆弱性

Argo Workflowsは、Kubernetes上での並列ジョブのオーケストレーションのためのオープンソースのコンテナネイティブワークフローエンジンです。バージョン3.7.14および4.0.5より前のバージョンでは、Workflow作成権限を持つユーザーがtemplateReferencing: Strictをバイパスし、ホストネットワークへのアクセス、サービスアカウントの切り替え、Podセキュリティコンテキストの上書き、制御プレーンノードへのスケジューリングのためのトレランス追加、またはSAトークンマウントの有効化を行うことが可能でした。これは、この機能の目的を損なう行為です。実際の影響は、Kubernetesレベルでどのような制御があるかによります。PodSecurity AdmissionやOPA/Gatekeeperを使用しているクラスターでは、一部機能（例えばhostNetworkの使用）を独自にブロックします。ArgoのStrictモードを主な強制レイヤーとしているクラスターは完全に曝露されます。この問題はバージョン3.7.14および4.0.5で修正されました。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-007792Argo Project AuthorsのArgo Workflowsにおける不正な認証に関する脆弱性

Argo Workflowsは、Kubernetes上で並列ジョブをオーケストレーションするためのオープンソースのコンテナネイティブワークフローエンジンです。バージョン2.9.0から4.0.2未満および3.7.11において、Workflowを提出できるユーザーは、Workflow提出時にpodSpecPatchフィールドを含めることで、WorkflowTemplateに定義されたすべてのセキュリティ設定を完全に回避できます。これは、controllerがtemplateReferencing: Strictに設定されている場合でも機能し、templateReferencing: Strictはユーザーを管理者承認済みテンプレートに制限する仕組みとして特に文書化されています。提出されたWorkflowのpodSpecPatchフィールドは、specマージ時に参照されたWorkflowTemplateよりも優先され、作成時にセキュリティ検証なしで直接Pod仕様に適用されます。この脆弱性はバージョン4.0.2および3.7.11で修正されています。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
argo-workflows: >= 4.0.0, < 4.0.2, >= 2.9.0, < 3.7.11
Fixed
Action
For Red Hat OpenShift AI 2.25.5 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.redhat.com/en/documentation/red_hat_openshift_ai/
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 11 Mar 2026 · Last source change 15 Jul 2026, 01:08 UTC · CWE-863 · Incorrect Authorization

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-11206
Product sourceCNA
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    >= 4.0.0, < 4.0.2; >= 2.9.0, < 3.7.11 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    >= 4.0.0, < 4.0.2; >= 2.9.0, < 3.7.11 · Fixed: For Red Hat OpenShift AI 2.25.5 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.redhat.com/en/documentation/red_hat_openshift_ai/
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Mitigation reference recorded
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-11206↗Red Hat Product Security security advisory↗CISA Vulnrichment SSVC evidence↗Public exploit reference · GitHub GHSA-3WF5-G532-RCRR↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-31892 · cve.blacktree.nl