search menu icon-carat-right cmu-wordmark

CERT Coordination Center

Bisheng has authentication bypass vulnerabilities

Vulnerability Note VU#166125

Original Release Date: 2026-10-14 | Last Revised: 2026-10-14

Overview

Bisheng contains three vulnerabilities: a pre-authentication account takeover mechanism via a legacy single sign-on (SSO) endpoint; an Insecure Direct Object Reference (IDOR) vulnerability that exposes cross-user workflow data; and prior to version 2.5.0, authenticated attackers could perform cross-user LLM credential abuse and data disclosure due to missing service-layer access checks. Together, these flaws could allow unauthenticated attackers to gain administrative control while enabling authenticated users access to sensitive data and hardcoded credentials.

Description

Bisheng is an open-source Large Language Model (LLM) application DevOps platform, developed by DataElement, designed to assist in building, managing, and scaling LLMs.

CVE-2026-96679 (Legacy SSO Bypass) A vulnerability resides in the legacy SSO endpoint (POST /user/sso). The application processes incoming JSON payloads containing arbitrary usernames and issues a valid JSON Web Token (JWT) without enforcing any form of caller authentication, such as signature verification, shared secrets, or network allowlisting. Furthermore, if the provided username does not exist, the system automatically registers the account. If this newly generated account matches the configured administrative username or is the first user in the system, it is automatically granted super-administrator privileges.

CVE-2026-96681 (IDOR Workflow Exposure) There are missing authorization controls across multiple version retrieval endpoints. The underlying source code retrieves flow and workflow version records based on user-supplied parameters without performing any data ownership or permission validation. Any authenticated user can query and read the complete Domain-Specific Language (DSL) configurations belonging to other accounts.

CVE-2026-100156 (Credential Abuse & Access Control Skip) Within the assistant service's prompt auto-optimization feature, endpoints accept an assistant identifier from the caller without verifying whether the caller owned that assistant. An assistant identifier is a mechanism that lets users or systems recognize that content or interactions come from an AI assistant rather than a human.

Impact

Authentication Bypass / Account Takeover: The legacy SSO vulnerability (CVE-2026-96679) allows unauthenticated attackers to bind their session to an existing victim's profile by completely skipping JWT validation, potentially granting full super-administrative access, leading to full application compromise.

Unauthorized Data Disclosure: The IDOR vulnerability (CVE-2026-96681) causes a breach of data confidentiality, as the system fails to properly validate whether the authenticated user has permission to access the resource.

Resource and Credential Abuse: The assistant service vulnerability (CVE-2026-100156) allows authenticated attackers to run unauthorized AI inferences billed directly to another user's provider account (such as OpenAI, Azure, or Anthropic), while also leaking the victim assistant's configured tools and workflows.

Solution

The vendor has addressed two of the three discovered vulnerabilities in subsequent software releases. CERT/CC recommends upgrading to patched releases.

CVE-2026-100156: The vendor has remediated the assistant service vulnerability in version 2.5.0.

CVE-2026-96681: The vendor has remediated the IDOR workflow vulnerability in version 3.0.0.

For the remaining unpatched vulnerability (CVE-2026-96679), DataElement/Bisheng has not responded to multiple coordination efforts. CERT/CC suggests implementing the manual mitigations below until an official update becomes available.

CVE-2026-96679 Legacy SSO Vulnerability: Administrators should consider the following defensive measures:

  • Avoid setting BISHENGPRO=true in the environment configuration.
  • Disable or deprecate the legacy SSO endpoint entirely, or enforce global JWT validation. The affected function is sso(), located in src/backend/bisheng/user/api/user.py, affecting the API endpoint POST /user/sso.
  • Restrict access to the POST /user/sso network path to loopback/same-origin to provide defense-in-depth.

Acknowledgements

Thanks to Louis Sanchez, Voke Cyber, for reporting these vulnerabilities.

This vulnerability note was prepared by Laurie Tyzenhaus.

Vendor Information

166125
 

DataElem Unknown

Notified:  2026-08-06 Updated: 2026-10-14

CVE-2026-100156 Unknown
CVE-2026-96679 Unknown
CVE-2026-96681 Unknown

Vendor Statement

We have not received a statement from the vendor.


Other Information

CVE IDs: CVE-2026-100156 CVE-2026-96679 CVE-2026-96681
API URL: VINCE JSON | CSAF
Date Public: 2026-10-14
Date First Published: 2026-10-14
Date Last Updated: 2026-10-14 16:42 UTC
Document Revision: 2

Sponsored by CISA.