This vulnerability allows an attacker with access to a malicious or compromised repository to exploit an overly permissive environment variable allowlisting in the Crabbox configuration and serialize sensitive local environment variables—such as API tokens, cloud credentials, or broker tokens—into the remote command execution environment. The resulting information disclosure can expose credentials and secret data to the remote execution context, potentially enabling further exploitation such as unauthorized access to cloud resources or remote services. The weakness is classified as CWE‑94, indicating improper control of code generation, because the contaminated environment variables are effectively injected into remote command contexts.

Systems using the Openclaw Crabbox project that run any version prior to 0.12.0 are affected. The vulnerability exists in all releases of Crabbox from inception up to, but excluding, the 0.12.0 release. No specific operating system or platform is mentioned; the issue is confined to the Crabbox application itself. It is advisable to upgrade any affected Crabbox instance to version 0.12.0 or later to eliminate the risk.

The CVSS score of 9.3 signals a critical threat, while the EPSS score is presently unavailable, suggesting that the exploitation likelihood has not been quantified. The vulnerability is not listed in the CISA KEV catalog. Attackers typically need the ability to introduce or manipulate repository code that is processed by Crabbox, which can occur if a repository is publicly writable, compromised, or contains malicious content. Once the repository code or configuration is executed, environment variables containing secrets are propagated to the remote command environment, exposing credentials that can be used to gain unauthorized access to external systems or services. Due to the high severity and the simple conditions for exploitation—merely running Crabbox with a malicious or compromised repository—the risk remains high and immediate action is warranted.