Description

Kestra is an open-source, event-driven orchestration platform. Prior to 2.0.0-rc6, Kestra's worker/src/main/java/io/kestra/worker/endpoint/WorkerEndpoint.java serves GET /worker without authentication and serializes the complete live Task object, which can expose commands, environment variables, HTTP headers, connection details, plaintext credentials, and execution identifiers while the main API on port 8080 remains protected. This issue is fixed in 2.0.0-rc6.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "7.5",
  "pubDate": "2026-08-11T22:19:05.287Z",
  "pubdate": "2026-08-11T22:19:05.287Z",
  "executiveSummary": "An information disclosure vulnerability exists in Kestra prior to version 2.0.0-rc6, specifically within the worker endpoint component. The vulnerability is caused by an unauthenticated GET request handler that serializes and returns the complete live Task object. Attackers can exploit this flaw over the network without requiring authentication or privileges to harvest sensitive operational data. The impact of successful exploitation includes the exposure of critical secrets such as plain-text credentials, connection details, environment variables, commands, HTTP headers, and execution identifiers. This compromises the confidentiality of the orchestration platform and underlying infrastructure. The vulnerability is mitigated by upgrading the affected deployment to version 2.0.0-rc6 or later, where proper access controls and authentication are enforced on the worker endpoint.",
  "technicalDetails": "The vulnerability resides in the WorkerEndpoint.java component of Kestra, specifically within the request handling logic for the GET /worker route. The root cause of the security flaw is the lack of authentication mechanisms combined with over-permissive object serialization. While the main API operating on port 8080 implements appropriate security controls, the worker endpoint inadvertently exposes internal state without verifying the identity or authorization of the requester.\nDuring standard operation, the vulnerable endpoint serializes the entire live Task object into the HTTP response payload. Because the Task object contains comprehensive runtime context, its serialization results in the exposure of highly sensitive data structures. This includes plaintext credentials, underlying system commands, environment variables, HTTP headers, remote connection strings, and internal execution identifiers.\nThe attack flow proceeds as follows: An unauthenticated malicious actor sends a crafted HTTP GET request directly to the vulnerable worker endpoint exposed on the network. Because the endpoint does not enforce authentication or access restrictions, the application processes the request and invokes the serialization routine on the live Task object. The resulting payload, containing sensitive configuration and execution data, is returned directly in the HTTP response body to the attacker. No specific privileges or prior system access are required to initiate this request, provided the endpoint is reachable over the network.\nThe affected component is io/kestra/worker/endpoint/WorkerEndpoint.java within Kestra versions prior to 2.0.0-rc6. The post-exploitation impact includes the aggregation of credentials and environment variables, which can be leveraged to facilitate lateral movement, access external connected services, or orchestrate secondary attacks against the infrastructure managed by the orchestration platform."
}