Quick answers
- Is CVE-2026-54323 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54323 being exploited in the wild.
- How severe is CVE-2026-54323?
- Medium severity, with a CVSS score of 5.9, published 23 June 2026.
- Which products and versions are affected?
- Daytona < 0.185.0.
- Is there a fix for CVE-2026-54323?
- A patch was published on 2026-06-23: Fix released in version 0.185.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54323 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-54323?
- Check whether you run Daytona 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
A vulnerability in the Daytona daemon's git clone implementation (affecting both go-git and native git CLI paths) results in the disabling of TLS certificate verification. When a clone request includes credentials, the daemon transmits the HTTP Basic Authorization header over an unvalidated connection. A man-in-the-middle (MitM) attacker can present a spoofed certificate to capture Git personal access tokens or passwords and inject malicious repository content into the sandbox. This issue is specific to the clone operation, as pull and push operations already enforced verification. The vulnerability is addressed in version 0.185.0 by enforcing TLS verification by default.
Affected products
- Daytonaio Daytona < 0.185.0
Timeline
- 2026-06-09: advisory: GitHub advisory published by maintainers
- 2026-06-23: disclosed: CVE published to NVD
- 2026-06-23: patched: Fix released in version 0.185.0