Quick answers
- Is CVE-2026-53577 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53577 being exploited in the wild.
- How severe is CVE-2026-53577?
- Medium severity, with a CVSS score of 6.5, 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-53577?
- 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-53577 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-53577?
- 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 Insecure Direct Object Reference (IDOR) exists in the 'previewFileFromExecution' endpoint (GET /api/v1/{tenant}/executions/{executionId}/file/preview). The vulnerability is caused by 'ExecutionController.java' failing to validate the return value of the 'validateFile' method, which is intended to enforce execution-level and namespace-level isolation. While sibling methods correctly handle redirects when a user requests a file URI belonging to a different execution, the preview endpoint ignores this check and proceeds to fetch the file from storage. An attacker with low-privileged access can provide a 'kestra://' URI belonging to a victim's execution to retrieve sensitive output data. The issue is fixed 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 Security Advisory published by vendor
- 2026-06-26: disclosed: CVE published to NVD