CVE-2026-54319

MEDIUMPre-NVD 4.24.2—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% 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
4.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.2Exploit: None knownExposed: 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.186, a sandbox volume reference (volumeId, which may also be a volume name) was forwarded to the runner and used to build the host bind-mount source path without confinement. A reference containing path-traversal sequences could in principle resolve the mount source outside the intended per-volume base directory. This vulnerability is fixed in 0.186.

CVSS v3
4.2
EG Score
4.2(medium)
EG Risk
23(Track)
EG Risk 23/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity42% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

June 18, 2026

Last Modified

June 24, 2026

Advisory Details (1)

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

Sandbox volume reference path traversal in host mount-path construction (not exploitable in released versions) · Advisory · daytonaio/daytona · GitHub

Affected: v0.186.0. Volume references are now resolved to the canonical volume UUID

https://github.com/daytonaio/daytona/security/advisories/GHSA-fjv8-j4p5-cr9m

Vendor Advisories for CVE-2026-54319(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/daytonaio/daytona—0.186.0—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 49× 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-08-23 01:07 UTCEG score recompute
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-21 07:22 UTCEG score recompute
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-20 08:08 UTCEG score recompute
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 07:43 UTCEG score recompute
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 15:09 UTCEG score recompute
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 16:07 UTCEG score recompute
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 17:06 UTCEG score recompute
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-14 18:02 UTCEG score recompute
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-12 17:52 UTCEG score recompute
  20. 2026-08-12 13:51 UTCEPSS rescore
  21. 2026-08-11 18:50 UTCEG score recompute
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-09 20:47 UTCEG score recompute
  24. 2026-08-09 13:46 UTCEPSS rescore
  25. 2026-08-08 21:46 UTCEG score recompute
Show 71 more
  1. 2026-08-08 16:37 UTCEPSS rescore
  2. 2026-08-07 22:44 UTCEG score recompute
  3. 2026-08-06 23:42 UTCEG score recompute
  4. 2026-08-06 13:47 UTCEPSS rescore
  5. 2026-08-06 00:41 UTCEG score recompute
  6. 2026-08-05 19:17 UTCEPSS rescore
  7. 2026-08-05 01:40 UTCEG score recompute
  8. 2026-08-04 15:10 UTCEPSS rescore
  9. 2026-08-04 10:39 UTCEPSS rescore
  10. 2026-08-04 02:18 UTCEG score recompute
  11. 2026-08-03 10:36 UTCEPSS rescore
  12. 2026-08-02 04:11 UTCEG score recompute
  13. 2026-08-02 02:27 UTCEPSS rescore
  14. 2026-08-01 05:09 UTCEG score recompute
  15. 2026-08-01 04:16 UTCEPSS rescore
  16. 2026-07-31 03:51 UTCEG score recompute
  17. 2026-07-30 16:28 UTCEPSS rescore
  18. 2026-07-30 03:06 UTCEG score recompute
  19. 2026-07-30 01:30 UTCEPSS rescore
  20. 2026-07-29 01:44 UTCEG score recompute
  21. 2026-07-28 15:37 UTCEPSS rescore
  22. 2026-07-27 18:06 UTCEG score recompute
  23. 2026-07-26 17:20 UTCEG score recompute
  24. 2026-07-26 14:54 UTCEPSS rescore
  25. 2026-07-25 14:18 UTCEPSS rescore
  26. 2026-07-24 14:18 UTCEPSS rescore
  27. 2026-07-23 14:18 UTCEPSS rescore
  28. 2026-07-23 03:19 UTCEG score recompute
  29. 2026-07-22 14:08 UTCEPSS rescore
  30. 2026-07-21 15:25 UTCEPSS rescore
  31. 2026-07-20 17:08 UTCEPSS rescore
  32. 2026-07-19 14:31 UTCEPSS rescore
  33. 2026-07-19 14:31 UTCEPSS rescore
  34. 2026-07-19 02:29 UTCEPSS rescore
  35. 2026-07-18 10:04 UTCEPSS rescore
  36. 2026-07-16 17:03 UTCEPSS rescore
  37. 2026-07-15 16:57 UTCEPSS rescore
  38. 2026-07-15 16:57 UTCEPSS rescore
  39. 2026-07-15 02:00 UTCEPSS rescore
  40. 2026-07-15 02:00 UTCEPSS rescore
  41. 2026-07-13 22:31 UTCEPSS rescore
  42. 2026-07-13 06:13 UTCEPSS rescore
  43. 2026-07-13 06:13 UTCEPSS rescore
  44. 2026-07-12 05:46 UTCEPSS rescore
  45. 2026-07-11 08:27 UTCEPSS rescore
  46. 2026-07-11 08:27 UTCEPSS rescore
  47. 2026-07-09 19:10 UTCEPSS rescore
  48. 2026-07-09 19:10 UTCEPSS rescore
  49. 2026-07-08 15:16 UTCEPSS rescore
  50. 2026-07-08 15:16 UTCEPSS rescore
  51. 2026-07-07 13:46 UTCEPSS rescore
  52. 2026-07-07 13:46 UTCEPSS rescore
  53. 2026-07-06 16:27 UTCEPSS rescore
  54. 2026-07-06 16:27 UTCEPSS rescore
  55. 2026-07-06 02:23 UTCEPSS rescore
  56. 2026-07-06 02:23 UTCEPSS rescore
  57. 2026-07-05 02:31 UTCEPSS rescore
  58. 2026-07-05 02:30 UTCEPSS rescore
  59. 2026-07-04 06:31 UTCEPSS rescore
  60. 2026-07-04 06:31 UTCEPSS rescore
  61. 2026-07-01 15:07 UTCEPSS rescore
  62. 2026-06-30 23:22 UTCEPSS rescore
  63. 2026-06-29 14:06 UTCEPSS rescore
  64. 2026-06-29 14:06 UTCEPSS rescore
  65. 2026-06-28 14:07 UTCEPSS rescore
  66. 2026-06-28 04:56 UTCEPSS rescore
  67. 2026-06-28 04:56 UTCEPSS rescore
  68. 2026-06-27 03:08 UTCEPSS rescore
  69. 2026-06-25 13:49 UTCEPSS rescore
  70. 2026-06-24 14:05 UTCEPSS rescore
  71. 2026-06-18 17:46 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-54319?
CVE-2026-54319 is a medium vulnerability published on June 18, 2026. Daytona is a secure and elastic infrastructure runtime for AI-generated code execution and agent workflows. Prior to 0.186, a sandbox volume reference (volumeId, which may also be a volume name) was forwarded to the runner and used to build the host bind-mount source path without confinement. A…
When was CVE-2026-54319 disclosed?
CVE-2026-54319 was first published in the National Vulnerability Database on June 18, 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-54319 actively exploited?
CVE-2026-54319 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.8% of all scored CVEs.
What is the CVSS score of CVE-2026-54319?
CVE-2026-54319 has a CVSS v3 base score of 4.2 (NVD).
How do I remediate CVE-2026-54319?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54319, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54319

Explore →

Is Your Infrastructure Affected by CVE-2026-54319?

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

Start Free Scan →Browse All CVEs