Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-31892Published 2026-03-11

CVE-2026-31892 — argoproj argo-workflows

criticalPublic exploit1 PoC repo

As of 2026-07-15, CVE-2026-31892 is a CRITICAL-severity vulnerability in argoproj argo-workflows, CVSS v3.1 9.9, EPSS 0.6% (50.7th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-31892, most recently “Cryptojacking Campaign Exploiting Gogs (CVE-2026-52806) and Argo Workflows (CVE-2026-42296/CVE-2026-42295) Targets Managed Kubernetes Clusters”.

CVSS v3.1
9.9/10Critical
EPSS
0.6%Higher than 50.7% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
1Campaigns referencing it
Priority
9/10Threadlinqs triage score
Published
Updated 2026-07-15
CVSS v3.1 9.9 (CRITICAL) · CVSS v4.0 8.9 · EPSS 0.6% (higher than 50.7% of all scored CVEs) · Priority 9/10 · Published 2026-03-11

Last updated:

What is CVE-2026-31892?

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.

The record classifies CVE-2026-31892 under weakness classes CWE-863, CWE-807. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 230 days ago.

Severity and exploitation probability

CVSS v3.1 base score
9.9 — CRITICAL
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CVSS v4.0 base score
8.9
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
EPSS (FIRST)
0.6% probability of exploitation in the next 30 days, higher than 50.7% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
9/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-03-11, last modified 2026-07-15

Is CVE-2026-31892 being exploited?

Weaponised exploit code for CVE-2026-31892 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 26 in the Threadlinqs vulnerability feed.

Affected products and versions

Affected software packages:

  • go:github.com/argoproj/argo-workflows/v4 — patched in 4.0.2
  • go:github.com/argoproj/argo-workflows/v3 — patched in 3.7.11
  • go:github.com/argoproj/argo-workflows

How to fix CVE-2026-31892

Fixed versions are recorded for 2 packages: go:github.com/argoproj/argo-workflows/v4 4.0.2, go:github.com/argoproj/argo-workflows/v3 3.7.11. Vendor advisory: https://github.com/argoproj/argo-workflows/security/advisories/GHSA-3wf5-g532-rcrr. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-31892

1 tracked threat in the Threadlinqs corpus references CVE-2026-31892, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories, public proof-of-concept repositories. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch