CVE-2026-53576
Received Received - Intake
Authentication Bypass in Kestra Leading to Remote Code Execution

Publication date: 2026-06-26

Last updated on: 2026-06-26

Assigner: GitHub, Inc.

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 Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-26
Last Modified
2026-06-26
Generated
2026-06-27
AI Q&A
2026-06-27
EPSS Evaluated
N/A
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
kestra kestra to 1.3.21 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-94 The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
CWE-288 The product requires authentication, but the product has an alternate path or channel that does not require authentication.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in Kestra, an open-source event-driven orchestration platform, in versions prior to 1.0.45 and 1.3.21. The authentication filter for the REST API incorrectly treats any request whose path ends with /configs as a public endpoint and forwards it without requiring credentials. Because Kestra addresses resources by URL path segments chosen by the caller, an unauthenticated user can craft a request ending with /configs to bypass Basic Authentication entirely.

This bypass allows an attacker to create and run flows containing Shell or Process tasks that execute with root privileges inside the Kestra container. Since the official Docker setup mounts the Docker socket, root access inside the container effectively grants control over the host Docker daemon, leading to potential full host compromise.

Impact Analysis

This vulnerability can have severe impacts including unauthorized remote code execution with root privileges inside the Kestra container. Because the container has access to the host Docker daemon, an attacker can escalate privileges to the host system, potentially gaining full control over the host environment.

Such an attack can lead to data breaches, service disruption, unauthorized access to sensitive information, and compromise of other systems running on the host.

Mitigation Strategies

To mitigate this vulnerability, upgrade Kestra to version 1.0.45 or 1.3.21 or later, where the authentication filter issue has been fixed.

Avoid running Kestra containers with the Docker socket (/var/run/docker.sock) mounted if possible, as this allows root in the container to reach the host Docker daemon.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-53576. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart