A critical authentication bypass in the OpenBMB XAgent ShareServer WebSocket endpoint allows unauthenticated attackers to remotely steal sensitive interaction history and third-party API keys.

The vulnerability exists in the on_connect handler within XAgentServer/application/websockets/share.py, where the authentication check has been commented out. This allows any unauthenticated user to connect to the /ws/share/{interaction_id} endpoint and retrieve private execution data without valid credentials.

The exposure of plaintext third-party API keys represents a severe security failure that can lead to unauthorized access to external services, data breaches, and potential financial loss. Because the vulnerability allows for the retrieval of any interaction history by simply providing an interaction_id, an attacker can systematically scrape private agent data. Given the CVSS score of 7.3, this flaw presents a high risk to organizational integrity and confidentiality.

Immediate Action: As no official patch is currently available, administrators should immediately restrict access to the WebSocket endpoint at the network or firewall level. If possible, disable the affected ShareServer functionality until the vendor provides a security update that restores the check_user authentication logic.

Proactive Monitoring: Review application logs for unusual WebSocket connection requests or spikes in traffic to the /ws/share/ path. Monitor for unauthorized access attempts from unknown IP addresses that correlate with the interaction_id parameter.

Compensating Controls: Deploy a Web Application Firewall (WAF) or an API gateway to enforce strict authentication headers and rate-limiting for all WebSocket connections. Ensure that the application infrastructure is isolated from public access where possible.

Public Exploit Available: Yes — a functional proof-of-concept exists as detailed in the technical write-up provided by the researcher (YLChen-007) on GitHub.

Due to the ease of exploitation and the exposure of highly sensitive credential data, this vulnerability must be treated with high priority. Organizations utilizing OpenBMB XAgent 1.0.0 should isolate the affected services from external networks immediately and maintain strict monitoring until the vendor releases a corrective patch to re-enable mandatory authentication.