CVE-2026-54320

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 88% 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
8.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.4Exploit: 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.184.0, organization invitations could be accepted (and declined) by a user whose email matched the invitation but had not been verified. Daytona authenticates users via OIDC and matches an invitation's target email against the email in the caller's token, but the invitation accept and decline paths did not require that email to be verified, unlike organization creation, which already enforced verification. On identity providers that allow self-service signup and issue a session before the email is verified, an actor could register an address matching a pending invitation, leave it unverified, and accept the invitation, joining the target organization with the role the invitation carried (up to Owner). This vulnerability is fixed in 0.184.0.

CVSS v3
8.4
EG Score
8.4(medium)
EPSS
11.9%
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

Cross-tenant organization takeover via invitation acceptance with an unverified email · Advisory · daytonaio/daytona · GitHub

https://github.com/daytonaio/daytona/security/advisories/GHSA-m6hx-cffh-3f3h

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 74× 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-15 02:00 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-14 23:42 UTCEG score recompute
  4. 2026-07-14 10:31 UTCEG score recompute
  5. 2026-07-13 22:31 UTCEPSS rescore
  6. 2026-07-13 21:48 UTCEG score recompute
  7. 2026-07-13 09:08 UTCEG score recompute
  8. 2026-07-13 06:13 UTCEPSS rescore
  9. 2026-07-13 06:13 UTCEPSS rescore
  10. 2026-07-12 20:27 UTCEG score recompute
  11. 2026-07-12 07:47 UTCEG score recompute
  12. 2026-07-12 05:46 UTCEPSS rescore
  13. 2026-07-11 19:07 UTCEG score recompute
  14. 2026-07-11 08:27 UTCEPSS rescore
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-11 06:27 UTCEG score recompute
  17. 2026-07-10 17:48 UTCEG score recompute
  18. 2026-07-10 05:08 UTCEG score recompute
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-09 19:10 UTCEPSS rescore
  21. 2026-07-09 16:17 UTCEG score recompute
  22. 2026-07-09 03:36 UTCEG score recompute
  23. 2026-07-08 15:16 UTCEPSS rescore
  24. 2026-07-08 15:16 UTCEPSS rescore
  25. 2026-07-08 14:57 UTCEG score recompute
Show 49 more
  1. 2026-07-08 02:15 UTCEG score recompute
  2. 2026-07-07 13:46 UTCEPSS rescore
  3. 2026-07-07 13:46 UTCEPSS rescore
  4. 2026-07-07 13:34 UTCEG score recompute
  5. 2026-07-07 00:54 UTCEG score recompute
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 12:13 UTCEG score recompute
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 23:10 UTCEG score recompute
  12. 2026-07-05 10:24 UTCEG score recompute
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 21:45 UTCEG score recompute
  16. 2026-07-04 09:05 UTCEG score recompute
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-03 20:23 UTCEG score recompute
  20. 2026-07-03 07:44 UTCEG score recompute
  21. 2026-07-02 19:04 UTCEG score recompute
  22. 2026-07-02 06:22 UTCEG score recompute
  23. 2026-07-01 17:42 UTCEG score recompute
  24. 2026-07-01 15:07 UTCEPSS rescore
  25. 2026-07-01 05:02 UTCEG score recompute
  26. 2026-06-30 23:22 UTCEPSS rescore
  27. 2026-06-30 16:21 UTCEG score recompute
  28. 2026-06-30 03:41 UTCEG score recompute
  29. 2026-06-29 15:02 UTCEG score recompute
  30. 2026-06-29 14:06 UTCEPSS rescore
  31. 2026-06-29 14:06 UTCEPSS rescore
  32. 2026-06-29 02:22 UTCEG score recompute
  33. 2026-06-28 14:07 UTCEPSS rescore
  34. 2026-06-28 13:42 UTCEG score recompute
  35. 2026-06-28 04:56 UTCEPSS rescore
  36. 2026-06-28 04:56 UTCEPSS rescore
  37. 2026-06-28 01:02 UTCEG score recompute
  38. 2026-06-27 12:23 UTCEG score recompute
  39. 2026-06-27 03:08 UTCEPSS rescore
  40. 2026-06-26 23:43 UTCEG score recompute
  41. 2026-06-26 11:04 UTCEG score recompute
  42. 2026-06-25 22:13 UTCEG score recompute
  43. 2026-06-25 13:49 UTCEPSS rescore
  44. 2026-06-25 09:33 UTCEG score recompute
  45. 2026-06-24 20:53 UTCEG score recompute
  46. 2026-06-24 14:05 UTCEPSS rescore
  47. 2026-06-24 08:14 UTCEG score recompute
  48. 2026-06-23 19:34 UTCEG score recompute
  49. 2026-06-23 19:32 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-54320?
CVE-2026-54320 is a high 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.184.0, organization invitations could be accepted (and declined) by a user whose email matched the invitation but had not been verified. Daytona authenticates users via OIDC and…
When was CVE-2026-54320 disclosed?
CVE-2026-54320 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-54320 actively exploited?
CVE-2026-54320 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 11.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54320?
CVE-2026-54320 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-54320?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54320, 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-54320

Explore →

Is Your Infrastructure Affected by CVE-2026-54320?

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