Quick answers
- Is CVE-2026-73246 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-73246 being exploited in the wild.
- How severe is CVE-2026-73246?
- High severity, with a CVSS score of 7.5, published 11 August 2026.
- Which products and versions are affected?
- Kestra <=1.3.26.
- Is there a fix for CVE-2026-73246?
- A patch was published on 2026-08-11: Fixed in version 2.0.0-rc6 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-73246 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-73246?
- 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
The vulnerability is an authentication bypass and sensitive information exposure in Kestra's WorkerEndpoint (/worker GET endpoint on port 8081). The endpoint is marked as non-sensitive by default and returns a fully serialized live Task domain object containing unredacted environment variables, commands, headers, and credentials. The management listener on 8081 operates independently of the main API authentication (port 8080), meaning kestra.server.basic-auth does not protect it—a second, manual endpoints.all.basic-auth configuration is required. Attack vector is unauthenticated network access to port 8081 with no preconditions beyond one running task; the attacker can enumerate all active executions and harvest plaintext secrets. The vulnerability affects Kestra versions ≤1.3.26 and is fixed in 2.0.0-rc6.
Affected products
- Kestra Kestra <=1.3.26
Timeline
- 2026-08-07: disclosed
- 2026-08-11: patched: Fixed in version 2.0.0-rc6