CVE-2026-53577
Analyzed Analyzed - Analysis Complete

Access Control Bypass in Kestra Allows File Preview Exploitation

Vulnerability report for CVE-2026-53577, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-26

Last updated on: 2026-07-01

Assigner: GitHub, Inc.

Description

Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, the previewFileFromExecution endpoint (GET /api/v1/{tenant}/executions/{executionId}/file/preview) contains an access control bypass that allows any authenticated user to read output files from any other execution within the same tenant, bypassing execution-level and namespace-level isolation. 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-07-01
Generated
2026-07-17
AI Q&A
2026-06-27
EPSS Evaluated
2026-07-16
NVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
kestra kestra to 1.0.45 (exc)
kestra kestra From 1.1.0 (inc) to 1.3.21 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Kestra is an open-source, event-driven orchestration platform. Before versions 1.0.45 and 1.3.21, the previewFileFromExecution endpoint (GET /api/v1/{tenant}/executions/{executionId}/file/preview) had an access control bypass vulnerability. This flaw allowed any authenticated user to read output files from any other execution within the same tenant, effectively bypassing execution-level and namespace-level isolation controls.

Detection Guidance

This vulnerability can be detected by attempting to access the previewFileFromExecution endpoint (GET /api/v1/{tenant}/executions/{executionId}/file/preview) with an authenticated user account and checking if it is possible to read output files from executions that belong to other users within the same tenant.

A practical way to test this is to use HTTP request tools such as curl or similar to send a GET request to the vulnerable endpoint with different execution IDs that the authenticated user should not have access to. If the response returns file contents from other executions, the system is vulnerable.

  • Example curl command to test access: curl -i -H "Authorization: Bearer <token>" "https://<kestra-server>/api/v1/<tenant>/executions/<other_execution_id>/file/preview"
  • Replace <token> with a valid authentication token, <kestra-server> with your Kestra server address, <tenant> with your tenant identifier, and <other_execution_id> with an execution ID that belongs to another user.

If the response contains output files from executions not owned by the authenticated user, it indicates the presence of the access control bypass vulnerability.

Impact Analysis

This vulnerability can lead to unauthorized access to sensitive output files from other executions within the same tenant. An attacker with valid authentication could read data they should not have access to, potentially exposing confidential or sensitive information.

Compliance Impact

This vulnerability allows any authenticated user within the same tenant to bypass access controls and read output files from other executions, which compromises execution-level and namespace-level isolation.

Such unauthorized access to potentially sensitive data could lead to violations of data protection regulations like GDPR and HIPAA, which require strict access controls and data confidentiality.

Mitigation Strategies

To mitigate this vulnerability, upgrade Kestra to version 1.0.45 or 1.3.21 or later, where the access control bypass issue in the previewFileFromExecution endpoint is fixed.

Chat Assistant

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

EPSS Chart