CVE-2026-54323

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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
5.9
EG Score
5.9(medium)
EPSS
2.0%
KEV
Not listed

Published

June 23, 2026

Last Modified

June 24, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
Patch available. Sources: github.
github Patch Available

Git credential leak via git clone with TLS verification disabled · Advisory · daytonaio/daytona · GitHub

https://github.com/daytonaio/daytona/security/advisories/GHSA-375h-72g4-hc9c

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 18× in last 7d / 42× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-12 05:46 UTCEPSS rescore
  2. 2026-07-12 05:35 UTCEG score recompute
  3. 2026-07-11 06:27 UTCEG score recompute
  4. 2026-07-10 07:09 UTCEG score recompute
  5. 2026-07-09 19:10 UTCEPSS rescore
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-09 07:57 UTCEG score recompute
  8. 2026-07-08 15:16 UTCEPSS rescore
  9. 2026-07-08 15:16 UTCEPSS rescore
  10. 2026-07-08 08:48 UTCEG score recompute
  11. 2026-07-07 13:46 UTCEPSS rescore
  12. 2026-07-07 13:46 UTCEPSS rescore
  13. 2026-07-07 09:35 UTCEG score recompute
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 16:27 UTCEPSS rescore
  16. 2026-07-06 10:25 UTCEG score recompute
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-05 11:10 UTCEG score recompute
  20. 2026-07-05 02:31 UTCEPSS rescore
  21. 2026-07-05 02:30 UTCEPSS rescore
  22. 2026-07-04 12:02 UTCEG score recompute
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-04 06:31 UTCEPSS rescore
  25. 2026-07-03 12:53 UTCEG score recompute
Show 17 more
  1. 2026-07-02 12:32 UTCEG score recompute
  2. 2026-07-01 15:07 UTCEPSS rescore
  3. 2026-07-01 13:23 UTCEG score recompute
  4. 2026-06-30 23:22 UTCEPSS rescore
  5. 2026-06-30 14:14 UTCEG score recompute
  6. 2026-06-29 15:05 UTCEG score recompute
  7. 2026-06-28 15:55 UTCEG score recompute
  8. 2026-06-28 14:07 UTCEPSS rescore
  9. 2026-06-27 16:46 UTCEG score recompute
  10. 2026-06-27 03:08 UTCEPSS rescore
  11. 2026-06-26 17:37 UTCEG score recompute
  12. 2026-06-25 18:28 UTCEG score recompute
  13. 2026-06-25 13:49 UTCEPSS rescore
  14. 2026-06-24 19:19 UTCEG score recompute
  15. 2026-06-24 14:05 UTCEPSS rescore
  16. 2026-06-23 19:34 UTCEG score recompute
  17. 2026-06-23 19:32 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54323?
CVE-2026-54323 is a medium vulnerability published on June 23, 2026. 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…
When was CVE-2026-54323 disclosed?
CVE-2026-54323 was first published in the National Vulnerability Database on June 23, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54323 actively exploited?
CVE-2026-54323 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54323?
CVE-2026-54323 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-54323?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54323, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-54323

Explore →

Is Your Infrastructure Affected by CVE-2026-54323?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs