CVE-2026-53576
Prior to 1.0.45 and 1.3.21, the authentication filter for the REST API (@Filter("/api/v1/**")) treats any request whose path ends in /configs as the public instance-config endpoint and forwards it without a credential check. kestra addresses its…
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (3.19%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, the authentication filter for the REST API (@Filter("/api/v1/**")) treats any request whose path ends in /configs as the public instance-config endpoint and forwards it without a credential check. kestra addresses its resources by URL path segments that the caller chooses (/api/v1/{tenant}/flows/{namespace}, /api/v1/{tenant}/executions/{namespace}/{id}, /api/v1/{tenant}/namespaces/{namespace}/kv/{key}). An anonymous caller picks the literal configs as the final segment, and the request bypasses Basic-Auth entirely. Because the bypass reaches the flow-create and execution-trigger routes, an unauthenticated caller creates a flow containing a Shell or Process task and runs it. The task executes as root inside the kestra container. The official docker-compose.yml mounts /var/run/docker.sock, so root in the container reaches the host Docker daemon. This vulnerability is fixed in 1.0.45 and 1.3.21.
- CVSS 3.1
- 10.0 CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- EPSS
- 3.19% probability · 87th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-94, CWE-288
- Affected
- kestra/kestra
- Source
- security-advisories@github.com
References
- https://github.com/kestra-io/kestra/security/advisories/GHSA-2q47-568g-9h4fExploit, Vendor Advisory
- https://github.com/kestra-io/kestra/security/advisories/GHSA-2q47-568g-9h4fExploit, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.