CVE-2026-31892: WorkflowTemplate Security Bypass via podSpecPatch in Strict/Secure Reference Mode
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.55% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: argoproj argo-workflows 4.0.2.
Low priority for now. Upgrade to argoproj argo-workflows 4.0.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 11, 2026
- Updated
- Jul 15, 2026
- EPSS
- 0.5% · 46th percentile
- CWE
- CWE-863
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 8.9
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| argoproj | argo workflows | cpe:2.3:a:argoproj:argo_workflows |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
argoproj argo-workflows
- >= 4.0.0, < 4.0.2, >= 2.9.0, < 3.7.11affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- argoproj argo workflows2.9.0 and later · before 3.7.11
- argoproj argo workflows4.0.0 and later · before 4.0.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/argoproj/argo-workflows | from 0 | — |
| Go | github.com/argoproj/argo-workflows | from 2.9.0 | — |
| Go | github.com/argoproj/argo-workflows/v2 | from 2.9.0 | — |
| Go | github.com/argoproj/argo-workflows/v3 | before 3.7.11 | 3.7.11 |
| Go | github.com/argoproj/argo-workflows/v4 | before 4.0.2 | 4.0.2 |
Same product
argoproj: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-54526Argo Workflows: Incomplete fix for CVE-2026-31892: ArtifactGC.PodSpecPatch bypass of Strict/Secure templateReferencing35Monitor
- CVE-2025-62156argo-workflows Zip Slip path traversal allows arbitrary file write and container configuration overwrite35Monitor
- CVE-2026-42297Argo Workflows Is Missing Authorization in Sync ConfigMap Provider34Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-23960Jan 21, 2026 · Argo Workflows affected by stored XSS in the artifact directory listing29Monitor
- ← EarlierCVE-2026-28229Mar 11, 2026 · Argo Workflows has unauthorized access to Argo Workflows Template30Monitor
- Later →CVE-2026-40886Apr 23, 2026 · Argo Workflows: Unchecked annotation parsing in pod informer crashes Argo Workflows controller30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| argoproj argo-workflows | 4.0.2 · description | Vendor (CNA) |
| Go:github.com/argoproj/argo-workflows/v3 | 3.7.11 | Package registry (OSV) |
| Go:github.com/argoproj/argo-workflows/v4 | 4.0.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-4229659 days apartArgo Workflows has incomplete fix for CVE-2026-31892: hostNetwork, securityContext, serviceAccountName bypass templateReferencing Strict/Secure32Monitor
- CVE-2026-282290 days apartArgo Workflows has unauthorized access to Argo Workflows Template30Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.