CVE-2026-54323 Daytona: Git credential leak via git clone with TLS verification disabled

Medium 5.9 Published Updated

Attackers can intercept Git clone traffic to steal credentials and inject malicious code due to disabled TLS verification in the Daytona daemon.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
None listed

What is CVE-2026-54323?

CVE-2026-54323 is a medium-severity vulnerability in daytonaio daytona, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

Official description

Daytona is a secure and elastic infrastructure runtime for AI-generated code execution and agent workflows. Prior to 0.185.0, the daemon's git clone implementation disabled TLS certificate verification. When a clone request carried Git credentials, the daemon sent the HTTP Basic Authorization header to the remote over a connection whose certificate was never validated, on both the go-git and native git CLI code paths. An attacker able to intercept clone traffic could present any TLS certificate, capture the Git credentials supplied for the clone, and serve tampered repository content into the sandbox. This vulnerability is fixed in 0.185.0.

Weakness: CWE-295

Which versions are affected by CVE-2026-54323?

How do I fix CVE-2026-54323?

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

Is CVE-2026-54323 being exploited?

There is no known exploitation of CVE-2026-54323 in the wild and no public exploit code.

Sources

Also known as GHSA-375h-72g4-hc9c.

Is CVE-2026-54323 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free