Authorization Bypass in poco-claw Workspace API

Executive Summary

CVE-2026-15622 is an authorization bypass vulnerability in the poco-ai poco-claw software, specifically affecting versions up to 0.5.4. The flaw exists in the function get_workspace_file within the file executor_manager/app/api/v1/workspace.py of the Workspace API component.

The vulnerability allows attackers to manipulate the user_id argument in API requests. By doing so, they can bypass authorization checks and access workspace files belonging to other users. This occurs because the system trusts the caller-supplied user_id without proper authentication or validation, enabling unauthorized access to sensitive files if the attacker knows or guesses the target session_id and file path.

The issue affects multiple workspace-related routes, potentially allowing cross-user operations such as listing, archiving, or deleting workspaces. The vulnerability has been patched in later versions, and the fix involves hardening authentication mechanisms for the Executor Manager control-plane and executor proxy interfaces.

Useful 0 Not Useful 0

Detection Guidance

To detect CVE-2026-15622 on your network or system, you can check for unauthorized access to workspace files by monitoring API requests to the vulnerable endpoint. The vulnerability affects the Executor Manager component in poco-claw versions up to 0.5.4, specifically the workspace file API endpoint.

• Inspect network traffic or logs for requests to the endpoint /api/v1/workspace/file/{user_id}/{session_id} where the user_id parameter does not match the authenticated user. Look for patterns like GET requests with manipulated user_id values.
• Use a tool like curl to test if the endpoint is vulnerable by sending a request with a manipulated user_id. Example command: curl -v http://<target-host>/api/v1/workspace/file/victim-user/<victim-session-id>?path=test.txt. If the response returns file contents without proper authentication, the system is vulnerable.
• Check the version of poco-claw installed. If it is version 0.5.4 or earlier, the system is likely vulnerable. You can verify the version by checking the project's configuration files or running the application with version flags if supported.
• Review logs for unusual activity, such as repeated requests to workspace file endpoints with varying user_id values, which may indicate exploitation attempts.

Useful 0 Not Useful 0

Impact Analysis

If you are using an affected version of poco-ai poco-claw (up to 0.5.4), this vulnerability could have several impacts:

• Unauthorized access to sensitive files: Attackers could access files in your workspace, including source code, credentials, or other confidential information, if they know or guess your session_id and file path.
• Data leakage: Sensitive data stored in workspace files could be exposed to unauthorized parties, leading to potential data breaches.
• Cross-user operations: Attackers could perform actions like listing, archiving, or deleting workspaces belonging to other users, disrupting operations or causing data loss.
• Privilege escalation: If combined with other vulnerabilities, this flaw could allow attackers to escalate privileges within the system.

The vulnerability can be exploited remotely, increasing the risk of exposure. The CVSS scores indicate a moderate to high severity, reflecting the potential for significant impact.

Useful 0 Not Useful 0

Compliance Impact

This vulnerability could impact compliance with several common standards and regulations, depending on the nature of the data processed or stored by the affected system:

• GDPR (General Data Protection Regulation): If the poco-claw system processes personal data of EU citizens, unauthorized access to workspace files could lead to a data breach. GDPR requires organizations to implement appropriate security measures to protect personal data. Failure to do so could result in significant fines (up to 4% of global annual revenue or €20 million, whichever is higher) and reputational damage.
• HIPAA (Health Insurance Portability and Accountability Act): If the system handles protected health information (PHI), this vulnerability could lead to unauthorized disclosure of PHI, violating HIPAA's Privacy and Security Rules. Non-compliance with HIPAA can result in fines ranging from $100 to $50,000 per violation, with a maximum penalty of $1.5 million per year for each violation.
• PCI DSS (Payment Card Industry Data Security Standard): If workspace files contain payment card information, unauthorized access could violate PCI DSS requirements for protecting cardholder data. Non-compliance can lead to fines, increased transaction fees, or even the loss of the ability to process payment cards.
• Other regulations: Depending on the industry and jurisdiction, this vulnerability could also affect compliance with standards like SOX (Sarbanes-Oxley Act), FISMA (Federal Information Security Management Act), or industry-specific regulations that mandate data protection and access controls.

Organizations using the affected software should assess the types of data processed or stored in the system and determine the potential compliance risks. Promptly applying the available patch and implementing additional security measures can help mitigate these risks.

Useful 0 Not Useful 0

Mitigation Strategies

To mitigate CVE-2026-15622, follow these immediate steps to reduce the risk of exploitation:

• Upgrade poco-claw to the latest patched version. The vulnerability is fixed in versions released after 0.5.4. Refer to the patch commit 67fcc88505c57f77d3fcf04eb5b89425b10cbf48 for details on the security hardening measures.
• If upgrading is not immediately possible, apply temporary mitigations such as restricting access to the vulnerable endpoint. Use network-level controls like firewalls or reverse proxies to block unauthorized access to the /api/v1/workspace/file endpoint.
• Implement additional authentication and authorization checks for the workspace file API. Ensure that the user_id parameter in requests matches the authenticated user's identity. This can be done by validating session tokens or other authentication mechanisms before processing the request.
• Monitor and audit access to workspace files. Enable detailed logging for all requests to the vulnerable endpoint and review logs for suspicious activity, such as requests with mismatched user_id values.
• Rotate sensitive data, such as session tokens or credentials, that may have been exposed due to this vulnerability. This helps prevent further unauthorized access even if the system was previously compromised.

Useful 0 Not Useful 0