Trust Center

Title: API credential exposure in sandboxes — patched, rotation required if affected

Category: Security Advisory
Severity: High
Status: Resolved
Notify subscribers: Yes

On April 9, 2026, we patched a vulnerability that allowed API credentials passed via the Daytona CLI or SDK to be read from sandbox memory by anyone with shell access on the same sandbox. The fix was deployed and verified in every region the same day in under five hours from disclosure to full remediation. We have no evidence of exploitation.

Am I affected?

Yes, if you used the CLI or SDK to authenticate to a sandbox launched from the default snapshot (or a custom snapshot that still had sudo) at any point before April 9, 2026, 20:44 UTC.

No, if your sandboxes only run on custom snapshots without sudo or root.

What to do

If you're in scope, rotate any API keys, service account keys, and CI/CD credentials that were used in the affected window. Rotation lives in the dashboard under Settings → API Keys.

Then review your audit logs for that same window for any sandbox operations, key usage, or admin actions you can't attribute to a known source. If anything looks off, email security@daytona.io.

A successful exploit would look identical to normal API traffic in our logs, so we can't prove a clean negative. Please treat rotation as required, not precautionary.

More

Full write-up: Security Advisory: API Credential Exposure in Sandboxes
Questions: security@daytona.io