CyberRota Analysis
AI-GeneratedVersions 0.2.247 and earlier of Soft Machine are vulnerable due to improper authentication handling in the verifyContainerAuth() and authenticateWorkspaceHttp() functions, allowing any tenant to exploit the global CONTAINER_SHARED_SECRET to access and manipulate other tenants' workspaces. This critical vulnerability enables unauthorized read, write, and destructive actions across workspaces, posing a significant risk to data integrity and confidentiality. Organizations using affected versions should prioritize immediate remediation efforts to mitigate potential exploitation.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Soft Machine is a Virtual Machine–based agentic development environment / Cloud OS. In versions 0.2.247 and prior, two authentication helpers in /app/server.js — verifyContainerAuth() and authenticateWorkspaceHttp() — accept the global CONTAINER_SHARED_SECRET as a bearer token without verifying which workspace the caller belongs to. Because that secret is set identically on every container in the Fly app and is reachable from the user-facing process environment inside each workspace, any tenant can use it to authenticate to any other tenant's workspace API. The result is cross-workspace read, write, and destructive-restore primitives reachable from any paying customer's shell. The existing per-workspace token check (workspaceTokenMatches) protects the user-facing per-workspace token path, but the shared-secret bearer path bypasses it entirely. At time of publication, there are no publicly known patches.