CVE-2026-42183 json
Argo Workflows: SSO RBAC Delegation Nil Pointer Dereference DoS (gatekeeper.go)
published 2026-05-04 6 mo ago modified 2026-09-10 59 d ago also BIT-argo-workflows-2026-42183 , EUVD-2026-28891 , GHSA-p4gq-3vxj-f4jq , GO-2026-5527
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 31%
- public exploits
- 0
- none known
Summary
Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. From version 4.0.0 to before version 4.0.5, a nil pointer dereference in server/auth/gatekeeper.go rbacAuthorization() causes a panic (denial of service) for SSO users whose claims match a namespace-level RBAC rule but not an SSO-namespace rule, when SSO_DELEGATE_RBAC_TO_NAMESPACE=true. This issue has been patched in version 4.0.5.
Patch / fix
- go github.com/argoproj/argo-workflows/v4 4.0.5
- bitnami argo-workflows 4.0.5
- argo_workflows_project argo_workflows 4.0.5
- argoproj argo_workflows 4.0.5
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-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-2026-42183 updated cvss 5.3
github.com/argoproj/argo-workflows: Argo Workflows: Denial of Service via nil pointer dereference for SSO users
-
Red Hat OpenShift AI (RHOAI) rhoai/odh-ml-pipelines-driver-rhel8, rhoai/odh-ml-pipelines-driver-rhel9, rhoai/odh-ml-pipelines-launcher-rhel8, rhoai/odh-ml-pipelines-launcher-rhel9, rhoai/odh-ml-pipelines-api-server-v2-rhel8, rhoai/odh-ml-pipelines-api-server-v2-rhel9, +8 moreaffected: workaround, no fix available “Fix deferred”
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
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/argoproj/argo-workflows/security/advisories/GHSA-p4gq-3vxj-f4jq referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 2.3 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N |
| CNA | 4.0 | 2.3 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/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 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/argoproj/argo-workflows/v4 | >=4.0.0, <4.0.5 |
4.0.5 |
| bitnami | argo-workflows | >=4.0.0, <4.0.5 |
4.0.5 |
| go | github.com/argoproj/argo-workflows | all versions |
no fix listed |
| go | github.com/argoproj/argo-workflows/v2 | all versions |
no fix listed |
| go | github.com/argoproj/argo-workflows/v3 | all versions |
no fix listed |
Affected products
- argoproj argo-workflows
Classification
- Weakness
-
- CWE-476 NULL Pointer Dereference
References
-
github.com
/argoproj/argo-workflows/commit/c4cc17d0c034fa9a9cc01ef1af6c8016c93071d4
web, patch
-
github.com
/argoproj/argo-workflows/security/advisories/GHSA-p4gq-3vxj-f4jq
web, exploit, vendor-advisory, advisory
-
github.com
/argoproj/argo-workflows/releases/tag/v4.0.5
web, release-notes, article
-
nvd.nist.gov
/vuln/detail/CVE-2026-42183
advisory, web
-
github.com
/argoproj/argo-workflows
package
Sources
- CVE List CVE-2026-42183
- GitHub Advisory GHSA-p4gq-3vxj-f4jq
- NVD CVE-2026-42183
- OSV BIT-argo-workflows-2026-42183
- OSV GO-2026-5527
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.