Quick answers
- Is CVE-2026-53576 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53576 being exploited in the wild.
- How severe is CVE-2026-53576?
- Critical severity, with a CVSS score of 10, published 26 June 2026.
- Which products and versions are affected?
- Kestra < 1.0.45, >= 1.1.0, < 1.3.21.
- Is there a fix for CVE-2026-53576?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-53576 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-53576?
- Check whether you run Kestra at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An authentication bypass exists in Kestra's REST API filter due to improper path validation. The `AuthenticationFilter` uses a suffix-based check (`endsWith("/configs")`) to identify public configuration endpoints, which can be manipulated by an attacker who provides 'configs' as a resource identifier (e.g., namespace or flow ID). By crafting requests to endpoints like `/api/v1/{tenant}/flows/configs`, an unauthenticated attacker can bypass Basic-Auth to create and execute malicious flows. These flows execute as the root user within the Kestra container. In default deployments using the official docker-compose file, the container has access to the host's Docker socket, allowing the attacker to escalate privileges and achieve full host takeover. This issue is resolved in versions 1.0.45 and 1.3.21.
Affected products
- kestra-io kestra < 1.0.45, >= 1.1.0, < 1.3.21
Timeline
- 2026-06-03: advisory: GitHub advisory published by maintainers
- 2026-06-26: disclosed: NVD publication date