A critical authentication bypass in BISHENG before 3.0.0 lets unauthenticated remote attackers forge admin tokens using a hard-coded default JWT signing secret.
What Is It
CVE-2026-130840 is an authentication bypass in BISHENG, a project from dataelement. Versions before 3.0.0 use a hard-coded default jwt_secret in the AuthJwt component. Because the secret is fixed and public, an attacker can forge a valid HS256 token offline. The forged token names user_id 1 with the admin role. The attacker sends it as the access_token_cookie and the application accepts them as an administrator.
The weakness is classified as CWE-321 (Use of Hard-coded Cryptographic Key). VulnCheck disclosed the issue, and NVD published the record on 2026-11-17. Its NVD status is currently "Deferred."
Why It Matters
VulnCheck scores this as CVSS 3.1 9.8 (Critical), with vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The CVSS 4.0 score is 9.3 (Critical). The attack works over the network with low complexity, and it needs no privileges and no user interaction.
A successful attacker gets full administrative access to users, workspaces, knowledge bases and workflows. That means complete control of the application's data and configuration, with high impact to confidentiality, integrity and availability.
This CVE has no CISA KEV entry in the supplied data, so active exploitation in the wild is not confirmed. Still, the attack takes no credentials and the token can be forged offline, so any exposed instance still on the default secret should be treated as at risk.
What's Vulnerable
- Vendor: dataelement
- Product: BISHENG
- Affected versions: all versions before 3.0.0 (semver)
- Repository:
NVD lists no CPE entries for this record. The references point to the default secret in src/backend/bisheng/core/config/settings.py (tag v2.6.0-fix2, line 752).
Patch Status
The affected range ends before 3.0.0, which means 3.0.0 is the first unaffected version. Upgrade BISHENG to 3.0.0 or later. NVD also links a related upstream commit (b98e2bc) in the BISHENG repository. Since this is not a KEV entry, there is no CISA-mandated required action or due date.
Admins who cannot upgrade right away should check whether their deployment still uses the default jwt_secret. Any token signed with that default secret should be treated as untrustworthy.