dbcve.org
Improper Certificate ValidationWeakness · CWE-295

CVE-2026-54323

MEDIUM · 5.9 CVSS v3.1 Published 2026-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Daytona versions prior to 0.185.0, the daemon's git clone implementation disabled TLS certificate verification. When clone requests included Git credentials, the HTTP Basic Authorization header was transmitted over an unvalidated TLS connection on both go-git and native git CLI code paths, allowing a man-in-the-middle attacker to intercept credentials and inject tampered repository content.

MitigationUpgrade Daytona to version 0.185.0 or later, which re-enables TLS certificate verification in the git clone implementation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Daytona version
    Run 'daytona version' or check the binary metadata to retrieve the version number
    Affected if Version is lower than 0.185.0
  2. Confirm git clone feature is in use
    Review Daytona configuration files or operation logs for any git clone operations performed by the daemon
    Affected if Git clone operations have been executed using the Daytona daemon
  3. Verify git credentials are configured
    Inspect Daytona settings or environment where Git credentials (username/password, tokens, or SSH keys) are stored or passed to clone operations
    Affected if Git credentials are configured or passed during clone operations
  4. Check for network position vulnerability
    Assess whether the Daytona instance operates in a network where a man-in-the-middle attack on TLS connections is plausible (shared or untrusted networks)
    Affected if Daytona runs in an environment where untrusted network paths exist between the daemon and Git servers

You are affected if your Daytona version is below 0.185.0 and you have performed git clone operations with credentials configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Daytona to version 0.185.0 or later, which re-enables TLS certificate verification in the git clone implementation.

Recommended fix High confidence

0.185.0

  1. Identify the currently installed Daytona version using 'daytona version' or checking the deployment manifests
  2. Upgrade Daytona to version 0.185.0 or later by updating the deployment configuration or reinstalling with the new version
  3. Verify the upgrade was successful by running 'daytona version' and confirming the version is 0.185.0 or higher
  4. Test that git clone operations with credentials work properly over TLS-validated connections

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54323 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-54323 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data