External risk intelligence

BISHENG Authentication Bypass via Hard-coded JWT Secret Allows Admin Impersonation.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-130840

BISHENG is a platform for managing knowledge bases and workflows, which is typically deployed as a web-based application. Since it provides administrative access via web interfaces and authentication cookies, it is commonly deployed as an internet-facing or externally reachable web service, making the administrative surface accessible to network-based attackers.

Authentication Bypass

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a security vulnerability in BISHENG software that could allow unauthorized individuals to gain administrative control. The issue stems from a hard-coded security secret, enabling attackers to impersonate administrators without proper authentication and potentially access sensitive data and system functions. The main concern is confirming relevance and exposure to our environment.

  • Unauthorized access to administrative functions is possible.
  • Critical security flaw affects system integrity and data access.
  • Confirm if BISHENG is in use and assess exposure.

Attack Path

How an attacker could exploit the issue

An attacker can impersonate an administrator by exploiting a hard-coded secret used for signing authentication tokens. This allows them to forge a token offline, granting them full administrative control over various system resources.

  • No authentication required for access.
  • Forge a token using a default secret.
  • Gain administrative access to sensitive data.

Live Threat

Current exploitation, exposure, and threat context

An authentication bypass vulnerability in BISHENG could allow unauthenticated remote attackers to gain full administrative access. This occurs when a hard-coded default JWT secret is used, enabling attackers to impersonate administrators by forging a signed token. This could affect users, workspaces, knowledge bases, and workflows.

  • Administrative access to user data.
  • Forging JWT tokens to bypass authentication.
  • Unauthorized access to sensitive system data.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability affects BISHENG deployments, likely managed by platform or application owners responsible for the knowledge base and workflow management system. The first practical step is to locate all instances of BISHENG, determine their exposure, and identify the accountable teams for each instance to prioritize remediation.

  • Platform or application owners should lead.
  • Verify instance reachability and business criticality.
  • Plan remediation based on assessed risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is BISHENG?

BISHENG is an open-source platform designed for building and managing LLM-based applications. It provides a web-based interface for users to organize knowledge bases, orchestrate complex workflows, and manage system resources, often serving as the central engine for an organization's internal document processing and AI automation pipelines.

What does CWE-321 mean for CVE-2026-130840?

CWE-321 refers to the use of a hard-coded cryptographic key. In this case, BISHENG relies on a default, hard-coded secret to sign its authentication tokens. Because this secret is embedded directly in the software, it is not a unique, private value. Attackers can obtain this secret and use it to sign their own malicious tokens, effectively tricking the system into believing they are logged in as legitimate administrators.

How do attackers trigger this authentication bypass?

An attacker triggers this vulnerability by creating a fake JSON Web Token (JWT) offline using the known default secret. They must set the 'user_id' to 1 and assign themselves the administrator role within the token claims. Once generated, the attacker simply sends this forged token in the 'access_token_cookie' field with a web request. The system does not require any prior login or legitimate credentials to accept the request as valid.

Why should I care if my BISHENG instance is reachable?

According to Halo Surface Signal, BISHENG is typically deployed as a web application, making it a prime target for network-based threats. If your instance is internet-facing, any remote attacker can reach the authentication interface and exploit this secret to gain full control. Even in internal environments, this flaw allows any user with network access to the platform to escalate privileges to administrative level.

What steps should I take if I use BISHENG?

Your immediate priority is to identify all running instances of BISHENG within your environment and determine who manages them. Once located, verify if the version is older than 3.0.0, as these versions are affected. Coordinate with the relevant platform owners to restrict network access to these instances while you prepare to update to a patched version that removes the hard-coded secret.

References