VYPR
Vendor

Daytonaio

Products
1
CVEs
6
Across products
6
Status
Private

Products

1

Recent CVEs

6
  • CVE-2026-54320HigJun 23, 2026
    risk 0.48cvss 8.4epss 0.00

    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…

  • CVE-2026-54322HigJun 23, 2026
    risk 0.43cvss 7.7epss 0.00

    Daytona is a secure and elastic infrastructure runtime for AI-generated code execution and agent workflows. Prior to 0.185.0, Daytona's organization role update and delete endpoints authorized the caller as an owner of the organization named in the request path, but resolved and…

  • CVE-2026-54321HigJun 23, 2026
    risk 0.39cvss 7.0epss 0.00

    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,…

  • CVE-2026-54324MedJun 23, 2026
    risk 0.35cvss 6.5epss 0.00

    Daytona is a secure and elastic infrastructure runtime for AI-generated code execution and agent workflows. Prior to 0.185.0, a cross-tenant authorization flaw in Daytona's notification WebSocket gateway allowed any authenticated user to subscribe to another organization's…

  • CVE-2026-54323MedJun 23, 2026
    risk 0.31cvss 5.9epss 0.00

    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…

  • CVE-2026-54319MedJun 23, 2026
    risk 0.20cvss 4.2epss 0.00

    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…