GPU VulnDB

Database/Control plane, storage & DevOps

Apache DolphinScheduler: non-admin users can read admin-managed kubeconfig credentials

CVSS 7.1CVE-2026-71895Control plane, storage & DevOpscurated

Impact

Any authenticated DolphinScheduler user, including low-privilege ones, can retrieve the kubeconfig that an administrator registered for cluster-managed task execution. That file carries credentials usable directly against the Kubernetes API, outside DolphinScheduler's own permission model, so the workflow tool stops being the boundary. On a GPU fleet the registered kubeconfig is usually the one that can place pods on accelerator nodes: if it is bound to cluster-admin or a broadly scoped service account, the holder can read Secrets, schedule their own pods onto GPU nodes alongside other tenants' workloads, and persist in the cluster. The blast radius is exactly the RBAC granted to that service account, which in practice is rarely minimal.

Who can reach it

Any user with valid DolphinScheduler login credentials, no admin role needed, reachable over whatever network the DolphinScheduler API/UI is exposed on. Authentication is required.

What to do

Upgrade Apache DolphinScheduler to 3.4.3 (affected: 3.2.0 up to but not including 3.4.3) and restart the API server component. Because the credentials may already have been read, treat the exposed kubeconfig as compromised: rotate the service-account token or client certificate it embeds and re-register the cluster. Scope that service account down to the namespaces DolphinScheduler actually needs rather than cluster-admin. No node drain or reboot is involved.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.