Security readout for executives and security teams
Plain-English summary
Argo Workflows can let a low-privileged workflow submitter override administrator-approved template security settings. The issue affects strict or secure reference mode, so organizations relying on approved templates may have weaker isolation than expected. A successful bypass could affect confidentiality, integrity, and availability of Kubernetes workloads.
Executive priority
Treat this as urgent for clusters where Argo Workflows is multi-tenant or used to enforce approved execution templates. The issue undermines a security boundary administrators may explicitly depend on.
Technical view
In affected Argo Workflows versions, podSpecPatch supplied in a Workflow is merged after the referenced WorkflowTemplate and applied directly to the pod spec without security validation. This bypasses templateReferencing: Strict controls intended to restrict users to approved WorkflowTemplates.
Likely exposure
Exposure is likely where Argo Workflows versions 2.9.0 to before 3.7.11, or 4.0.0 to before 4.0.2, allow users or service accounts to submit Workflows.
Exploitation context
The bundle does not cite known active exploitation, and KEV is false. The vulnerability requires authenticated workflow submission privileges, but has low attack complexity and high potential impact once those privileges exist.
Researcher notes
The core issue is trust in user-controlled Workflow fields during template merge precedence. Evidence supports CWE-807 and CWE-863 classifications. The source bundle does not provide a broader affected-product list beyond argoproj argo-workflows and Red Hat references.
Mitigation direction
- Upgrade Argo Workflows to 3.7.11, 4.0.2, or later fixed releases.
- Restrict Workflow submission permissions until affected controllers are upgraded.
- Review vendor advisories for Red Hat packaged or downstream Argo Workflows deployments.
- Do not rely on templateReferencing: Strict alone as a complete control on vulnerable versions.
Validation and detection
- Inventory Argo Workflows controller versions across all Kubernetes clusters.
- Identify users and service accounts allowed to submit Workflows.
- Review Workflow submissions and audit logs for podSpecPatch usage.
- Confirm upgraded controllers are running fixed versions before restoring normal submission access.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-807: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-31892 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16redhat-SADPCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:H——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
8.9HighVector: 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
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-03-11T16:01:11.139Z: Reported to Red Hat.
- 2026-03-11T15:41:14.376Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/argoproj/argo-workflows/security/advisories/GHSA-3wf5-g532-rcrrCVE reference, GitHub_M · x_refsource_CONFIRM
- https://access.redhat.com/security/cve/CVE-2026-31892CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2446551CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-31892.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:10184CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Reliance on Untrusted Inputs in a Security Decision
Reliance on Untrusted Inputs in a Security Decision represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.