dbcve.org
CWE-613Weakness · CWE-613

CVE-2026-54321

HIGH · 7.0 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 →
79/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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. From 0.101.0 until 0.184.0, sandbox previews that were switched from public to private could remain reachable without authentication for a short period after the change, due to a cached visibility state that was not invalidated when the sandbox's visibility changed. This vulnerability is fixed in 0.184.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

A race condition in Daytona's sandbox preview system allows cached visibility state to persist after changing from public to private, enabling unauthenticated access during the cache invalidation window. The cached visibility state is not properly invalidated when sandbox visibility is modified.

MitigationUpgrade Daytona to version 0.184.0 or later where visibility cache invalidation is properly implemented.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

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

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. Check if sandbox preview feature is enabled
    Inspect Daytona's configuration files or runtime settings for the sandbox preview module. Look for configuration keys related to 'sandbox', 'preview', or 'visibility' in config files (typically in /etc/daytona/ or the application's config directory).
    Affected if The sandbox preview feature is enabled and running on Daytona versions prior to 0.184.0
  2. Determine installed Daytona version
    Run 'daytona version' or 'daytona --version' to retrieve the installed version. Alternatively, check package manager output: 'dpkg -l daytona' or 'rpm -qi daytona' depending on the system.
    Affected if The installed version is below 0.184.0 (the fixed version)
  3. Verify visibility cache behavior
    Create a test sandbox, set it to public, note the cached state, then change to private and immediately attempt unauthenticated access during the cache window. Inspect cache configuration in daytona.conf for 'cache_ttl', 'visibility_cache', or similar settings.
    Affected if Cached visibility state persists after modification and unauthenticated access is granted during the cache window
  4. Check for cached visibility artifacts
    Examine cache directories (commonly /var/cache/daytona/ or similar) for visibility state files. Use 'find' to locate files containing 'visibility' or 'public/private' status in the cache layer.
    Affected if Stale visibility cache entries exist that do not reflect recent visibility changes

The environment is affected if Daytona sandbox preview is enabled, the installed version is below 0.184.0, and cached visibility state fails to invalidate upon visibility changes.

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.184.0 or later where visibility cache invalidation is properly implemented.

Recommended fix High confidence

0.184.0

  1. Identify the currently installed Daytona version using `daytona version` or checking your deployment manifests
  2. Upgrade to version 0.184.0 or later using your package manager or deployment method (e.g., `daytona upgrade` or redeploy with the new version)
  3. Verify the upgrade was successful by running `daytona version` to confirm the installed version
  4. Test that sandbox visibility changes (public to private) take effect immediately without caching delays

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54321 — 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-54321 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