The vulnerability in OpenClaw (CVE-2026-43569) stemmed from a failure to properly distinguish between trusted (e.g., bundled, user-configured) and untrusted (workspace-specific) plugin providers during non-interactive authentication setup. An attacker could craft a malicious workspace plugin that defined an authentication provider choice with an ID identical to a legitimate, trusted provider (e.g., 'openai-api-key').
When a user or an automated script initiated a non-interactive onboarding process using this choice ID, the system would not prioritize the trusted provider. Instead, it could resolve to the malicious workspace plugin. This would trigger the auto-enabling of the untrusted plugin, potentially allowing it to intercept sensitive credentials or execute unauthorized actions.
The core of the issue was in functions responsible for resolving and selecting these authentication providers, such as applyNonInteractivePluginProviderChoice and resolveManifestProviderAuthChoices. These functions lacked the necessary logic to check the origin of a plugin and prioritize trusted sources.
The patch addresses this by implementing a clear priority system based on the plugin's origin (config > bundled > global > workspace). It modifies the provider discovery and selection functions to filter out untrusted workspace plugins by default during setup and to always prefer choices from more trusted origins when ID collisions occur. This ensures that even if a malicious workspace plugin tries to shadow a legitimate provider, the trusted provider will be selected, mitigating the risk.