GPU VulnDB

Database/Control plane, storage & DevOps

Kestra: fast SHA-512 admin password hash allows offline cracking and cluster token theft

CVSS 8.7CVE-2026-55069Control plane, storage & DevOpscurated

Impact

Kestra is an event-driven orchestrator used to drive pipeline and batch work. It stores the BasicAuth administrator password as a plain fast SHA-512 digest, so anyone who gets read access to the backing PostgreSQL database can recover the admin password offline at high throughput. With the admin account, a Kubernetes-hosted Kestra becomes a path to the cluster ServiceAccount token and every Secret it can read - which on a fleet running orchestrated training jobs typically means registry credentials, object-store keys and the ability to schedule arbitrary workloads on GPU nodes. The flaw needs a prior database read, so it is an escalation primitive rather than an entry point.

Who can reach it

Anyone with read access to Kestra's PostgreSQL database (a database credential, a backup, a replica, or an SQL-injection foothold elsewhere). Cracking is offline and unauthenticated against Kestra itself.

What to do

Upgrade Kestra to 1.3.24 and restart the service. Rotate the administrator password after upgrading, since the old hash may already be in an attacker's hands, and rotate the Kestra ServiceAccount token and any Secrets it could read if database exposure is suspected. Daemon restart only; no node maintenance.

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.