Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Low severity, with a CVSS score of 3.1, published 2 December 2025.
- Which products and versions are affected?
- Nocobase up to 1.9.21; @nocobase/auth (npm) SEMVER:introduced=0,fixed=1.9.23.
- Is there a fix for This vulnerability?
- Yes. @nocobase/auth (npm): upgrade to 1.9.23 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a web application.
- Am I affected?
- Check whether you run Nocobase or @nocobase/auth (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @nocobase/auth (npm): upgrade to 1.9.23 or later
npm install @nocobase/auth@1.9.23
Technical details
The vulnerability exists in the JWT Service component (jwt-service.ts) which uses a hardcoded or easily discoverable default API_KEY/APP_KEY for signing and verifying JSON Web Tokens. The issue affects docker-compose deployments where administrators do not override the default JWT secret during setup. Although the official documentation recommends changing the secret, it is not enforced, leaving many deployments vulnerable. An attacker with network access can craft valid JWTs for any user, including administrators, without authentication. The fix was released in version 1.9.23.
Affected products
- NocoBase NocoBase up to 1.9.21
Timeline
- 2025-12-02: disclosed
- 2025-12-09: other: Advisory withdrawn as duplicate of GHSA-mv7p-34fv-4874
- 2025-12-02: patched: Fixed in version 1.9.23