CVE-2026-130840
9.8CriticalPublished 17 Nov 2026 · NVD status: Deferred · AI triage by gemini-3.1-flash-lite
Critical
0CVSS v3.110
- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User action
- None
- Impact
- Full C/I/A compromise
- Weakness
- CWE-321
What an attacker gets
Unauthenticated attackers can gain full administrative access to your entire BISHENG instance. They only need network access to the application to forge an admin JWT using the known hard-coded secret.
Root cause
The application uses a hard-coded default JWT signing secret for authentication.
Affected versions
BISHENG before 3.0.0
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Fix & remediation
Upgrade to BISHENG 3.0.0 or later. If you cannot upgrade immediately, manually override the JWT_SECRET environment variable in your deployment configuration with a strong, unique random string.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
BISHENG before 3.0.0 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to impersonate administrators by abusing a hard-coded default jwt_secret used by AuthJwt. Attackers can forge an HS256 token offline naming user_id 1 with the admin role, send it as access_token_cookie, and gain full administrative access to users, workspaces, knowledge bases and workflows.
References
- https://github.com/dataelement/bisheng/blob/v2.6.0-fix2/src/backend/bisheng/core/config/settings.py#L752
- https://github.com/dataelement/bisheng/commit/b98e2bc5c819a6a8d35538d91eab85833bd77703
- https://www.vulncheck.com/advisories/bisheng-before-3.0.0-authentication-bypass-via-hard-coded-jwt-signing-secret