Cyber Resilience

CVE-2026-55069

Crypto Weakness in Kestra ≤ 1.3.24

Public PoCCrypto Weakness
Published
26 June 2026
Modified
01 July 2026
Patch / advisory
CVSS Score v3.1 8.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
EPSS Score 0.0019 9th percentile
Risk Priority 59 floored blend · peak EPSS

Summary

CVE-2026-55069 is a high-severity Use of Password Hash With Insufficient Computational Effort (CWE-916) vulnerability in Kestra Kestra. Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Brute Force (T1110); ranked at the 9th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) and IA-5 (Authenticator Management) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Kestra is an open-source, event-driven orchestration platform. Prior to 1.3.24, this vulnerability exists in the BasicAuth authentication component of the Kestra OSS workflow orchestration platform. An attacker who gains read access to the PostgreSQL database can exploit SHA-512's high computation…

more

speed to recover the administrator password offline. In Kubernetes deployments, a successful crack further enables reading of the cluster ServiceAccount Token and all K8s Secrets, achieving vertical privilege escalation. This vulnerability is fixed in 1.3.24.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
T1110.002 Password Cracking Credential Access
Adversaries may use password cracking to attempt to recover usable credentials, such as plaintext passwords, when credential material such as password hashes are obtained.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-45807Same product: Kestra Kestra
CVE-2026-38428Same product: Kestra Kestra
CVE-2026-53576Same product: Kestra Kestra
CVE-2026-33664Same product: Kestra Kestra
CVE-2026-49869Same product: Kestra Kestra
CVE-2026-34612Same product: Kestra Kestra
CVE-2026-29082Same product: Kestra Kestra
CVE-2026-49984Same product: Kestra Kestra
CVE-2026-53577Same product: Kestra Kestra
CVE-2024-5743Shared CWE-916

Affected Assets

kestra
kestra
≤ 1.3.24

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V11.4.2

Mitigating Controls (NIST 800-53 r5) AI

Cryptographic protection mandates selection and use of approved algorithms whose parameters can include sufficient work factors for password hashing.

Authenticator management requires secure generation, distribution, and storage of passwords, directly enforcing computationally expensive hashing schemes.

Protection of information at rest requires cryptographic safeguards on stored password hashes, reducing exposure to offline cracking.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.DS-01 mostly match
prevents

Proper password hashing is a direct instance of using cryptographic hashes to protect data-at-rest.

PR.PS-06 mostly match
prevents

Secure development practices explicitly include selection and configuration of strong, computationally expensive password hashes.

PR.AA-03 partial match
prevents

Authentication policies may reference password handling but do not address storage or computational cost of hashes.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

degrades

Requires secure handling of authentication information, which includes choosing strong password hashing schemes.

prevents

Requires appropriate use of cryptography, which encompasses selecting strong hashing algorithms for passwords.

prevents

Secure coding practices include implementing password storage with adequate computational effort.

degrades

Mandates secure authentication mechanisms, directly addressing the need for computationally strong password hashes.

References