Skip to content
Fencer Vulns
high 7.5

CVE-2024-53862 json

Argo Workflows Allows Access to Archived Workflows with Fake Token in `client` mode

published 2024-12-02 23 mo ago modified 2026-09-10 1 mo ago also BIT-argo-workflows-2024-53862 , EUVD-2024-3475 , GHSA-h36c-m3rf-34h9 , GO-2024-3303

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 51%
public exploits
0
none known

Summary

Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. When using `--auth-mode=client`, Archived Workflows can be retrieved with a fake or spoofed token via the GET Workflow endpoint: `/api/v1/workflows/{namespace}/{name}` or when using `--auth-mode=sso`, all Archived Workflows can be retrieved with a valid token via the GET Workflow endpoint: `/api/v1/workflows/{namespace}/{name}`. No authentication is performed by the Server itself on `client` tokens. Authentication & authorization is instead delegated to the k8s API server. However, the Workflow Archive does not interact with k8s, and so any token that looks valid will be considered authenticated, even if it is not a k8s token or even if the token has no RBAC for Argo. To handle the lack of pass-through k8s authN/authZ, the Workflow Archive specifically does the equivalent of a `kubectl auth can-i` check for respective methods. In 3.5.7 and 3.5.8, the auth check was accidentally removed on the GET Workflow endpoint's fallback to archived workflows on these lines, allowing archived workflows to be retrieved with a fake token. This vulnerability is fixed in 3.6.2 and 3.5.13.

Patch / fix

  • go github.com/argoproj/argo-workflows/v3 3.5.13, 3.6.2
  • bitnami argo-workflows 3.6.2
  • argoproj argo-workflows 3.5.13, 3.6.2
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20241209T183251-1.1

opensuse advisories openSUSE-SU-2024:14567-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-53862 updated cvss 5.3

argo-workflows: Argo Workflows Allows Access to Archived Workflows with Fake Token in `client` mode

  • Red Hat OpenShift AI (RHOAI) odh-ml-pipelines-driver-container, odh-ml-pipelines-launcher-container, odh-ml-pipelines-api-server-v2-container, odh-ml-pipelines-persistenceagent-v2-container, odh-ml-pipelines-scheduledworkflow-v2-container, odh-data-science-pipelines-argo-argoexec-container, +1 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
23 mo ago

Exploit prediction

0.66% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/argoproj/argo-workflows/security/advisories/GHSA-h36c-m3rf-34h9 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 6.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N
CNA 4.0 6.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/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 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/argoproj/argo-workflows/v3
>=3.5.7, <3.5.13
>=3.6.0, <3.6.2
>=3.6.0-rc1, <3.6.2
3.5.13
3.6.2
bitnami argo-workflows
>=3.5.7, <3.6.2
3.6.2
go github.com/argoproj/argo-workflows
all versions
 no fix listed
go github.com/argoproj/argo-workflows/v2
all versions
 no fix listed

Affected products

  • argoproj argo-workflows

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-290 Authentication Bypass by Spoofing

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.