Skip to main content
VulnerabilityPublished Updated

CVE-2026-73246: kestra · Information Exposure

Affects kestraSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 1.3.31 soon.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.3.31
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Upgrade kestra to 1.3.31.

Affected software

ProductAffectedFixed in
kestra-iokestraAffected
  • <1.3.31
Fixed in
  • 1.3.31
GitHubkestra-io/kestrapkg:github/kestra-io/kestraOther threatsAffected
  • =2.0.0-rc6
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to Kestra version 2.0.0-rc6 or later where this vulnerability is fixed. Patch status is not explicitly confirmed but the description states the issue is fixed in 2.0.0-rc6.

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.

References

Community reviews

Loading reviews…