Unauthenticated administrator impersonation via default JWT secret
Published Dec 2, 2025 · Updated Dec 2, 2025
Authentication bypass in NocoBase 1.9.0 through 1.9.21 and 2.0.0-alpha.1 through 2.0.0-alpha.51 allows remote attackers to forge JWTs. The official one-click Docker configuration supplied a public default APP_KEY value that the JWT service used to sign and verify tokens instead of requiring a deployment-unique secret. The affected ranges also include 1.9.0-beta.17 and earlier; only Docker deployments retaining the default key are exposed, and a token for a known userId receives that user's permissions, including administrator access.
Summary
What happened
Authentication bypass in NocoBase 1.9.0 through 1.9.21 and 2.0.0-alpha.1 through 2.0.0-alpha.51 allows remote attackers to forge JWTs. The official one-click Docker configuration supplied a public default APP_KEY value that the JWT service used to sign and verify tokens instead of requiring a deployment-unique secret. The affected ranges also include 1.9.0-beta.17 and earlier; only Docker deployments retaining the default key are exposed, and a token for a known userId receives that user's permissions, including administrator access.
The record
- CVE
- CVE-2025-13877
- Published
- Dec 2, 2025
- Updated
- Dec 2, 2025
- Vendor
- NocoBase
- Product
- NocoBase
- Classifications
- CWE-320, CWE-321, T1606
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 2, 2025CVE publishedPublication date reported by the CVE source.
- Dec 2, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.9.0
- Affected versionversion=1.9.1
- Affected versionversion=1.9.2
- Affected versionversion=1.9.3
- Affected versionversion=1.9.4
- Affected versionversion=2.0.0-alpha.0
- Affected versionversion=2.0.0-alpha.1
- Affected versionversion=2.0.0-alpha.10
- Affected versionversion=2.0.0-alpha.11
- Affected versionversion=2.0.0-alpha.12
- Affected versionversion=2.0.0-alpha.13
- Affected versionversion=2.0.0-alpha.14
- Affected versionversion=2.0.0-alpha.15
- Affected versionversion=2.0.0-alpha.16
- Affected versionversion=2.0.0-alpha.17
- Affected versionversion=2.0.0-alpha.18
- Affected versionversion=2.0.0-alpha.19
- Affected versionversion=2.0.0-alpha.2
- Affected versionversion=2.0.0-alpha.20
- Affected versionversion=2.0.0-alpha.21
- Affected versionversion=2.0.0-alpha.22
- Affected versionversion=2.0.0-alpha.23
- Affected versionversion=2.0.0-alpha.24
- Affected versionversion=2.0.0-alpha.25
- Affected versionversion=2.0.0-alpha.26
- Affected versionversion=2.0.0-alpha.27
- Affected versionversion=2.0.0-alpha.28
- Affected versionversion=2.0.0-alpha.29
- Affected versionversion=2.0.0-alpha.3
- Affected versionversion=2.0.0-alpha.30
- Affected versionversion=2.0.0-alpha.31
- Affected versionversion=2.0.0-alpha.32
- Affected versionversion=2.0.0-alpha.33
- Affected versionversion=2.0.0-alpha.34
- Affected versionversion=2.0.0-alpha.35
- Affected versionversion=2.0.0-alpha.36
- Affected versionversion=2.0.0-alpha.37
- Affected versionversion=2.0.0-alpha.4
- Affected versionversion=2.0.0-alpha.5
- Affected versionversion=2.0.0-alpha.6
- Affected versionversion=2.0.0-alpha.7
- Affected versionversion=2.0.0-alpha.8
- Affected versionversion=2.0.0-alpha.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- NocoBase default-key JWT forgery proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo