CVE-2026-54323: CWE-295: Improper Certificate Validation in daytonaio daytona
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.
AI Analysis
Technical Summary
CVE-2026-54323 is an improper certificate validation vulnerability (CWE-295) in daytonaio's Daytona product. Before version 0.185.0, the daemon disables TLS certificate verification during git clone operations. When Git credentials are included in the clone request, the daemon sends the HTTP Basic Authorization header over an unvalidated TLS connection. An attacker capable of intercepting this traffic can present any TLS certificate, capture credentials, and inject malicious repository content into the sandbox environment. This vulnerability is resolved in Daytona 0.185.0.
Potential Impact
An attacker who can intercept network traffic during a git clone operation can bypass TLS certificate validation, capture Git credentials, and serve malicious repository content. This compromises confidentiality of credentials and integrity of the code executed in the sandbox, potentially leading to unauthorized code execution or data exposure. The CVSS score of 5.9 reflects a medium severity with high confidentiality impact and low integrity impact.
Mitigation Recommendations
Upgrade Daytona to version 0.185.0 or later, where this vulnerability is fixed by enabling proper TLS certificate validation during git clone operations. No other mitigations are indicated. Patch status is not explicitly stated but the fix is included in version 0.185.0.
CVE-2026-54323: CWE-295: Improper Certificate Validation in daytonaio daytona
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.
CVSS v3.1
Score 5.9medium
Affected software
pkg:golang/github.com/daytonaio/daytonaRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-54323 is an improper certificate validation vulnerability (CWE-295) in daytonaio's Daytona product. Before version 0.185.0, the daemon disables TLS certificate verification during git clone operations. When Git credentials are included in the clone request, the daemon sends the HTTP Basic Authorization header over an unvalidated TLS connection. An attacker capable of intercepting this traffic can present any TLS certificate, capture credentials, and inject malicious repository content into the sandbox environment. This vulnerability is resolved in Daytona 0.185.0.
Potential Impact
An attacker who can intercept network traffic during a git clone operation can bypass TLS certificate validation, capture Git credentials, and serve malicious repository content. This compromises confidentiality of credentials and integrity of the code executed in the sandbox, potentially leading to unauthorized code execution or data exposure. The CVSS score of 5.9 reflects a medium severity with high confidentiality impact and low integrity impact.
Mitigation Recommendations
Upgrade Daytona to version 0.185.0 or later, where this vulnerability is fixed by enabling proper TLS certificate validation during git clone operations. No other mitigations are indicated. Patch status is not explicitly stated but the fix is included in version 0.185.0.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-12T18:42:02.223Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3acbe4eed863c81e6c9a65
Added to database: 06/23/2026, 18:09:40 UTC
Last enriched: 06/30/2026, 23:17:10 UTC
Last updated: 08/05/2026, 00:41:15 UTC
Views: 56
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.