Git credential theft via unverified clone TLS
Published Jun 23, 2026 · Updated Jun 23, 2026
Improper certificate validation in Daytona before 0.185.0 allows man-in-the-middle attackers to steal Git credentials during clones. The daemon disables certificate verification in both go-git and native git CLI clone paths while forwarding HTTP Basic credentials. Exploitation requires a credentialed clone through an attacker-controlled network position, enabling credential capture and tampered repository content.
Summary
What happened
Improper certificate validation in Daytona before 0.185.0 allows man-in-the-middle attackers to steal Git credentials during clones. The daemon disables certificate verification in both go-git and native git CLI clone paths while forwarding HTTP Basic credentials. Exploitation requires a credentialed clone through an attacker-controlled network position, enabling credential capture and tampered repository content.
The record
- CVE
- CVE-2026-54323
- Published
- Jun 23, 2026
- Updated
- Jun 23, 2026
- Vendor
- Daytona Platforms, Inc.
- Product
- Daytona
- Classifications
- CWE-295, CAPEC-475, CAPEC-459, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 23, 2026CVE publishedPublication date reported by the CVE source.
- Jun 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.185.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo