CVE-2026-4959
Authentication Bypass in OpenBMB XAgent ShareServer WebSocket Endpoint
Publication date: 2026-03-27
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openbmb | xagent | 1.0.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-306 | The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. |
| CWE-287 | When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in OpenBMB XAgent 1.0.0 allows unauthenticated attackers to access and steal sensitive user interaction histories and unmasked third-party API keys due to missing authentication and authorization checks.
This exposure of sensitive information can lead to violations of data protection regulations such as GDPR and HIPAA, which require strict controls over personal and sensitive data to prevent unauthorized access and disclosure.
Specifically, the lack of authentication and ownership verification means that personal data and credentials can be accessed by unauthorized parties, undermining confidentiality and potentially resulting in non-compliance with standards mandating data privacy and security.
Can you explain this vulnerability to me?
CVE-2026-4959 is a critical vulnerability in OpenBMB XAgent 1.0.0 affecting the ShareServer WebSocket endpoint at `/ws/share/{interaction_id}`. The vulnerability arises because the authentication function `check_user()` is completely disabled, allowing any attacker to connect without proper authentication or authorization.
Attackers can manipulate the `interaction_id` parameter to bypass identity verification and retrieve any user's full interaction history, including sensitive data. Additionally, third-party API keys are stored in plaintext in the database, which attackers can steal through this vulnerability.
This flaw allows unauthenticated remote attackers to access sensitive information without needing valid credentials, special tools, or exploiting path traversal, making it a severe security risk especially in multi-tenant or SaaS deployments.
How can this vulnerability impact me? :
This vulnerability can lead to complete disclosure of sensitive user data and credentials. An attacker can remotely connect to the vulnerable WebSocket endpoint without authentication and retrieve full user interaction histories.
Specifically, attackers can steal unmasked third-party API keys such as RapidAPI keys, SurveyMethods credentials, and Amazon scraper tokens, which are stored in plaintext in the database.
The impact includes unauthorized access to confidential information, potential misuse of stolen API keys, and exposure of all user interactions, which can compromise the security and privacy of affected users and organizations.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by attempting to connect to the XAgent server's ShareServer WebSocket endpoint at `/ws/share/{interaction_id}` without valid authentication credentials.
Since the authentication check is missing, an unauthenticated WebSocket connection will be accepted, allowing retrieval of user interaction data.
A practical detection method is to use WebSocket client tools or command-line utilities to connect to the endpoint with fabricated credentials and send a JSON message `{"type": "shared"}` to see if interaction data is returned.
- Use `websocat` or `wscat` to connect to the WebSocket endpoint: `wscat -c ws://<target>/ws/share/<interaction_id>`
- After connection, send the message: `{"type": "shared"}`
- If the server responds with interaction data including API keys or user histories without requiring valid authentication, the vulnerability is present.
Additionally, monitoring network traffic for WebSocket connections to `/ws/share/` endpoints and inspecting if unauthorized data is transmitted can help detect exploitation attempts.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting network access to the vulnerable WebSocket endpoint `/ws/share/{interaction_id}` to trusted users only.
Implement firewall rules or network segmentation to block unauthenticated external access to the XAgent ShareServer WebSocket endpoint.
If possible, disable or temporarily shut down the ShareServer WebSocket service until a patch or fix is available.
Monitor logs and network traffic for suspicious WebSocket connections and unauthorized data access attempts.
Contact the vendor or maintainers for updates or patches addressing the missing authentication and authorization checks.