Read the docs
TI-2025-12681 Aliases CVE-2025-13877GHSA-mv7p-34fv-4874

nocobase JWT Service jwt-service.ts hard-coded key

Priority MEDIUM 61CWE-320Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Attack requirements
None
Impact type
Security bypass
Confidentiality · integrity · availability
Low · Low · Low
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA and GitHub. Impact type from CWE-321.

Summary

A vulnerability was detected in nocobase up to 1.9.4/2.0.0-alpha.37. The affected element is an unknown function of the file nocobase\packages\core\auth\src\base\jwt-service.ts of the component JWT Service. The manipulation of the argument API_KEY results in use of hard-coded cryptographic key . The attack can be launched remotely. A high complexity level is associated with this attack. The exploitability is described as difficult. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00328 26th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by the CNA
Fix Fixed @nocobase/auth (npm): 1.9.23, 1.9.0-beta.18, 2.0.0-alpha.52

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
—nocobase1.9.0; 1.9.1; 1.9.2; 1.9.3; 1.9.4; 2.0.0-alpha.0; 2.0.0-alpha.1; 2.0.0-alpha.2; 2.0.0-alpha.3; 2.0.0-alpha.4; 2.0.0-alpha.5; 2.0.0-alpha.6; 2.0.0-alpha.7; 2.0.0-alpha.8; 2.0.0-alpha.9; 2.0.0-alpha.10; 2.0.0-alpha.11; 2.0.0-alpha.12; 2.0.0-alpha.13; 2.0.0-alpha.14; 2.0.0-alpha.15; 2.0.0-alpha.16; 2.0.0-alpha.17; 2.0.0-alpha.18; 2.0.0-alpha.19; 2.0.0-alpha.20; 2.0.0-alpha.21; 2.0.0-alpha.22; 2.0.0-alpha.23; 2.0.0-alpha.24; 2.0.0-alpha.25; 2.0.0-alpha.26; 2.0.0-alpha.27; 2.0.0-alpha.28; 2.0.0-alpha.29; 2.0.0-alpha.30; 2.0.0-alpha.31; 2.0.0-alpha.32; 2.0.0-alpha.33; 2.0.0-alpha.34; 2.0.0-alpha.35; 2.0.0-alpha.36; 2.0.0-alpha.37—No fix listedCNA
—@nocobase/auth (npm)1.9.0 to before 1.9.231.9.23Patch availableGHSA-mv7p-34fv-4874
—@nocobase/auth (npm)before 1.9.0-beta.181.9.0-beta.18Patch availableGHSA-mv7p-34fv-4874
—@nocobase/auth (npm)2.0.0-alpha.1 to before 2.0.0-alpha.522.0.0-alpha.52Patch availableGHSA-mv7p-34fv-4874
  • nocobase Vendor— Affected 1.9.0; 1.9.1; 1.9.2; 1.9.3; 1.9.4; 2.0.0-alpha.0; 2.0.0-alpha.1; 2.0.0-alpha.2; 2.0.0-alpha.3; 2.0.0-alpha.4; 2.0.0-alpha.5; 2.0.0-alpha.6; 2.0.0-alpha.7; 2.0.0-alpha.8; 2.0.0-alpha.9; 2.0.0-alpha.10; 2.0.0-alpha.11; 2.0.0-alpha.12; 2.0.0-alpha.13; 2.0.0-alpha.14; 2.0.0-alpha.15; 2.0.0-alpha.16; 2.0.0-alpha.17; 2.0.0-alpha.18; 2.0.0-alpha.19; 2.0.0-alpha.20; 2.0.0-alpha.21; 2.0.0-alpha.22; 2.0.0-alpha.23; 2.0.0-alpha.24; 2.0.0-alpha.25; 2.0.0-alpha.26; 2.0.0-alpha.27; 2.0.0-alpha.28; 2.0.0-alpha.29; 2.0.0-alpha.30; 2.0.0-alpha.31; 2.0.0-alpha.32; 2.0.0-alpha.33; 2.0.0-alpha.34; 2.0.0-alpha.35; 2.0.0-alpha.36; 2.0.0-alpha.37 Fixed in — No fix listed CNA
  • @nocobase/auth (npm) Vendor— Affected 1.9.0 to before 1.9.23 Fixed in 1.9.23 Patch available GHSA-mv7p-34fv-4874
  • @nocobase/auth (npm) Vendor— Affected before 1.9.0-beta.18 Fixed in 1.9.0-beta.18 Patch available GHSA-mv7p-34fv-4874
  • @nocobase/auth (npm) Vendor— Affected 2.0.0-alpha.1 to before 2.0.0-alpha.52 Fixed in 2.0.0-alpha.52 Patch available GHSA-mv7p-34fv-4874

Remediation

  • Fix · GHSA-mv7p-34fv-4874 @nocobase/auth (npm) Fixed in 1.9.23 Advisory →
  • Fix · GHSA-mv7p-34fv-4874 @nocobase/auth (npm) Fixed in 1.9.0-beta.18 Advisory →
  • Fix · GHSA-mv7p-34fv-4874 @nocobase/auth (npm) Fixed in 2.0.0-alpha.52 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2025-13877
  2. 2026-10-03 Alias added: GHSA-mv7p-34fv-4874

References

Sources