Skip to main content
CVE-2025-13877VulnerabilityPublished

CVE-2025-13877: nocobase · Use of Hard-coded Cryptographic Key

Affects nocobaseSource CVE Database V5

0

Not known to be exploited · CVSS 6.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
npmnocobasepkg:npm/nocobaseOther threatsAffected
  • =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–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately audit their nocobase deployments to identify affected versions. Implement strict access controls on API endpoints to limit exposure. Monitor JWT token usage for anomalies, such as unexpected token issuances or invalid signatures. Employ network-level protections like Web Application Firewalls (WAFs) to detect and block suspicious requests targeting the JWT service. Consider isolating or segmenting systems running nocobase to reduce lateral movement risk. Stay alert for vendor updates or community patches and plan for timely upgrades once available. Finally, conduct security awareness training for developers and administrators emphasizing secure key management practices to prevent similar issues.

Description

CVE-2025-13877 is a medium severity vulnerability in nocobase versions up to 1.9.4 and 2.0.0-alpha.37 involving the use of a hard-coded cryptographic key in the JWT Service component. This flaw allows remote attackers to potentially manipulate the API_KEY argument, compromising the cryptographic integrity of JWT tokens. Exploitation is difficult due to high attack complexity and no user interaction or privileges are required. The vulnerability impacts confidentiality, integrity, and availability at a low level and has a CVSS 4.0 score of 6.

References

Community reviews

Loading reviews…