CVE-2026-53576: Kestra: Unauthenticated RCE via /configs path-suffix auth-filter bypass

Published Jun 26, 2026
·
Updated

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.

Affected Software

4 affected components
Kestra Kestra<1.0.45
Kestra Kestra<1.3.21
Kestra Kestra<1.0.45
Kestra Kestra>=1.1.0<1.3.21

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Kestra to a version that resolves this vulnerability.

    Fixed in 1.0.45
  2. Upgrade

    Upgrade Kestra to a version that resolves this vulnerability.

    Fixed in 1.3.21
  3. Configuration

    Update docker-compose.yml to not mount /var/run/docker.sock into the Kestra container to prevent container-root from reaching the host Docker daemon.

    Kestra docker-compose.yml /var/run/docker.sock mount = remove
  4. Compensating control

    Apply network/access controls so that the Kestra REST API path-suffixes that could reach /api/v1/** (including endpoints that use path segments for tenant/namespace) are not reachable by unauthenticated callers (e.g., restrict inbound traffic to trusted clients and require authentication at the network/WAF/reverse-proxy layer).

Event History

Jun 26, 2026
CVE Published
via MITRE·08:54 PM
Data Sourced
via MITRE·08:54 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-53576?

The severity of CVE-2026-53576 is rated as critical with a score of 10.

2

How do I fix CVE-2026-53576?

To fix CVE-2026-53576, upgrade Kestra to version 1.0.45 or 1.3.21 or later.

3

What kind of vulnerability is CVE-2026-53576?

CVE-2026-53576 is classified as an unauthenticated remote code execution (RCE) vulnerability.

4

What components are affected by CVE-2026-53576?

CVE-2026-53576 affects the Kestra REST API due to an authentication filter bypass.

5

What could be the impact of CVE-2026-53576?

The impact of CVE-2026-53576 allows attackers to execute arbitrary code on the server without authentication.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203