# CVE-2026-73246: Kestra: Unauthenticated management `/worker` endpoint exposes live task configuration and plaintext credentials

> Unauthenticated access to the /worker endpoint exposes live task configurations and plaintext credentials, allowing attackers to read sensitive data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-m65f-q5gj-hg46

## What is CVE-2026-73246?

CVE-2026-73246 is a high-severity vulnerability in kestra-io kestra, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-73246?


## How do I fix CVE-2026-73246?

No fix has been published for CVE-2026-73246 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-73246 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73246 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73246 and fix it if it is affected.

What it is: CVE-2026-73246 is a high-severity vulnerability in kestra-io kestra, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73246 exists.

Affected product: kestra-io kestra. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73246/ (Markdown: https://insights.sbomify.com/CVE-2026-73246/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73246
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73246
- OSV: https://osv.dev/vulnerability/CVE-2026-73246

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73246/
Summaries are generated and may contain mistakes; the official description above is the record.