# CVE-2026-130840: BISHENG before 3.0.0 Authentication Bypass via Hard-coded JWT Signing Secret


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-cm6c-9mm3-95m4

## What is CVE-2026-130840?

CVE-2026-130840 is a critical vulnerability in dataelement BISHENG, published on 17 Nov 2026. 

### Official 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.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2026-130840?

1 open source package ship an affected version, including dataelement/bisheng.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `dataelement/bisheng` | GitHub | `pkg:github/dataelement/bisheng` | All versions | 3.0.0 |

## How do I fix CVE-2026-130840?

Upgrade dataelement/bisheng to 3.0.0 or later.

## Is CVE-2026-130840 being exploited?

There is no known exploitation of CVE-2026-130840 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130840 and fix it if it is affected.

What it is: CVE-2026-130840 is a critical vulnerability in dataelement BISHENG, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130840 in the wild and no public exploit code.

Affected packages and fixed versions:
- dataelement/bisheng (GitHub): affected all versions; fixed in 3.0.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130840/ (Markdown: https://insights.sbomify.com/CVE-2026-130840/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130840
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130840
- OSV: https://osv.dev/vulnerability/CVE-2026-130840

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130840/
Summaries are generated and may contain mistakes; the official description above is the record.
