Vulnerabilities in pkg:npm/@nocobase/auth

PACKAGE
Advisory Identifier: GHSA-mv7p-34fv-4874
Advisory Summary

CVE-2025-13877 is a MODERATE authentication bypass vulnerability (CWE-321: Use of Hard-coded Cryptographic Key) affecting @nocobase/auth libraries in the npm ecosystem. The issue involves authentication bypass via default jwt secret in nocobase docker-compose deployments. Remediation is available by upgrading affected packages to version 1.9.23, 1.9.0-beta.18, 2.0.0-alpha.52.

2 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/@nocobase/auth

2 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/@nocobase/auth. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-mv7p-34fv-4874 CVE-2025-13877 MODERATE Authentication Bypass via Default JWT Secret in NocoBase docker-compose Deployments
GHSA-644f-hrff-mf96 - LOW Duplicate Advisory: Authentication Bypass via Default JWT Secret in NocoBase docker-compose Deployments

CVE-2025-13877 at a Glance

CVE Identifier CVE-2025-13877
GHSA Identifier GHSA-mv7p-34fv-4874
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-321: Use of Hard-coded Cryptographic Key
Affected Product @nocobase/auth
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2025-13877

To remediate this vulnerability, upgrade all affected @nocobase/auth dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@nocobase/auth fixed: 1.9.23
npm install @nocobase/auth@1.9.23
@nocobase/auth fixed: 1.9.0-beta.18
npm install @nocobase/auth@1.9.0-beta.18
@nocobase/auth fixed: 2.0.0-alpha.52
npm install @nocobase/auth@2.0.0-alpha.52
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @nocobase/auth

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2025-13877, inspect your project dependencies using npm:

npm ls @nocobase/auth

Analyze the terminal output to locate any version of @nocobase/auth in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.9.23), your application is affected.

Note: The npm ls @nocobase/auth command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-321: Use of Hard-coded Cryptographic Key, where the product uses a hard-coded, unchangeable cryptographic key. In @nocobase/auth, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact CVE-2025-13877 is an **authentication bypass vulnerability caused by insecure default JWT key usage** in NocoBase Docker deployments. Because the official one-click Docker deployment configuration historically provided a **public default JWT key**, attackers can **forge valid JWT tokens without possessing any legitimate credentials**. By constructing a token with a known `userId` (commonly the administrator account), an attacker can directly bypass authentication and authorization checks. Successful exploitation allows an attacker to: - Bypass authentication entirely - Impersonate arbitrary users - Gain full administrator privileges - Access sensitive business data - Create, modify, or delete users - Access cloud storage credentials and other protected secrets The vulnerability is **remotely exploitable**, requires **no authentication**, and **public proof-of-concept exploits are available**. This issue is functionally equivalent in impact to other JWT secret exposure vulnerabilities such as **CVE-2024-43441** and **CVE-2025-30206**. Deployments that used the default Docker configuration without explicitly overriding the JWT secret are affected. --- ### Patches ✅ The vulnerability has been **fully patched** through a secure JWT key management redesign. The remediation enforces the following security guarantees: - JWT secrets are no longer allowed to fall back to public default values. - Secrets must either: - Be explicitly provided by the user, or - Be securely generated using cryptographically strong randomness at first startup. - Generated secrets are persisted securely with restricted filesystem permissions. - Invalid or weak secret values immediately trigger a startup failure. ✅ Fixed Versions: - **NocoBase ≥ 1.9.23** - **NocoBase ≥ 1.9.0-beta.18** - **NocoBase ≥ 2.0.0-alpha.52** --- ### Workarounds If upgrading is not immediately possible, the following temporary mitigations **must** be performed to reduce risk: 1. Explicitly set a **strong, randomly generated JWT secret** via environment variables `APP_KEY`. 2. **Restart all running NocoBase instances** so the new secret takes effect. 3. **Invalidate all existing JWT sessions**, forcing complete user re-authentication. 4. Verify that **no default secret values** are present in: - `docker-compose.yml` - `.env` files - Kubernetes Secrets --- ### References - **CVE Record:** CVE-2025-13877 - **VulDB Entry:** https://vuldb.com/?id.334033 - **Public Exploit Proof:** https://gist.github.com/H2u8s/f3ede60d7ecfe598ae452aa5a8fbb90d - **Affected Default Docker Configurations:** - https://github.com/nocobase/nocobase/blob/main/docker/app-mysql/docker-compose.yml#L13 - https://github.com/nocobase/nocobase/blob/main/docker/app-mariadb/docker-compose.yml#L13 - https://github.com/nocobase/nocobase/blob/main/docker/app-postgres/docker-compose.yml#L11 - https://github.com/nocobase/nocobase/blob/main/docker/app-sqlite/docker-compose.yml#L11 - **Official Deployment Documentation:** - https://docs.nocobase.com/welcome/getting-started/installation/docker-compose - https://v2.docs.nocobase.com/get-started/installation/docker

CVE-2025-13877 Affected @nocobase/auth Versions

3 component(s)
Fixed Versions:
1.9.231.9.0-beta.182.0.0-alpha.52
Product / Package Ecosystem Affected Versions Fixed Version
@nocobase/auth
npm
≥ 1.9.0
< 1.9.23
1.9.23
@nocobase/auth
npm
< 1.9.0-beta.18
1.9.0-beta.18
@nocobase/auth
npm
≥ 2.0.0-alpha.1
< 2.0.0-alpha.52
2.0.0-alpha.52

References

Frequently Asked Questions

What is CVE-2025-13877?
CVE-2025-13877 is a security vulnerability in @nocobase/auth involving Authentication Bypass via Default JWT Secret in NocoBase docker-compose Deployments under CWE-321: Use of Hard-coded Cryptographic Key.
Which @nocobase/auth versions are affected?
Affected versions include releases prior to 1.9.23, 1.9.0-beta.18, 2.0.0-alpha.52 across affected packages: @nocobase/auth.
What version fixes CVE-2025-13877?
Upgrading to 1.9.23, 1.9.0-beta.18, 2.0.0-alpha.52 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @nocobase/auth affected?
Yes, @nocobase/auth is affected in releases prior to 1.9.23, 1.9.0-beta.18, 2.0.0-alpha.52. Upgrade your dependency to 1.9.23, 1.9.0-beta.18, 2.0.0-alpha.52 or later.
What CWE is associated with CVE-2025-13877?
CVE-2025-13877 is classified under CWE-321: Use of Hard-coded Cryptographic Key (The product uses a hard-coded, unchangeable cryptographic key.).
How can I check npm dependencies for CVE-2025-13877?
Run the dependency tree command: 'npm ls @nocobase/auth'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-mv7p-34fv-4874",
  "modified" : "2025-12-09T17:42:53Z",
  "published" : "2025-12-09T17:42:53Z",
  "aliases" : [ "CVE-2025-13877" ],
  "summary" : "Authentication Bypass via Default JWT Secret in NocoBase docker-compose Deployments",
  "details" : "### Impact\n\nCVE-2025-13877 is an **authentication bypass vulnerability caused by insecure default JWT key usage** in NocoBase Docker deployments.\n\nBecause the official one-click Docker deployment configuration historically provided a **public default JWT key**, attackers can **forge valid JWT tokens without possessing any legitimate credentials**. By constructing a token with a known `userId` (commonly the administrator account), an attacker can directly bypass authentication and authorization checks.\n\nSuccessful exploitation allows an attacker to:\n\n- Bypass authentication entirely\n- Impersonate arbitrary users\n- Gain full administrator privileges\n- Access sensitive business data\n- Create, modify, or delete users\n- Access cloud storage credentials and other protected secrets\n\nThe vulnerability is **remotely exploitable**, requires **no authentication**, and **public proof-of-concept exploits are available**.  \nThis issue is functionally equivalent in impact to other JWT secret exposure vulnerabilities such as **CVE-2024-43441** and **CVE-2025-30206**.\n\nDeployments that used the default Docker configuration without explicitly overriding the JWT secret are affected.\n\n---\n\n### Patches\n\n✅ The vulnerability has been **fully patched** through a secure JWT key management redesign.\n\nThe remediation enforces the following security guarantees:\n\n- JWT secrets are no longer allowed to fall back to public default values.\n- Secrets must either:\n  - Be explicitly provided by the user, or\n  - Be securely generated using cryptographically strong randomness at first startup.\n- Generated secrets are persisted securely with restricted filesystem permissions.\n- Invalid or weak secret values immediately trigger a startup failure.\n\n✅ Fixed Versions:\n- **NocoBase ≥ 1.9.23**\n- **NocoBase ≥ 1.9.0-beta.18**\n- **NocoBase ≥ 2.0.0-alpha.52**\n\n---\n\n### Workarounds\n\nIf upgrading is not immediately possible, the following temporary mitigations **must** be performed to reduce risk:\n\n1. Explicitly set a **strong, randomly generated JWT secret** via environment variables `APP_KEY`.\n2. **Restart all running NocoBase instances** so the new secret takes effect.\n3. **Invalidate all existing JWT sessions**, forcing complete user re-authentication.\n4. Verify that **no default secret values** are present in:\n   - `docker-compose.yml`\n   - `.env` files\n   - Kubernetes Secrets\n\n---\n\n### References\n\n- **CVE Record:** CVE-2025-13877  \n- **VulDB Entry:** https://vuldb.com/?id.334033  \n- **Public Exploit Proof:**  \n  https://gist.github.com/H2u8s/f3ede60d7ecfe598ae452aa5a8fbb90d  \n\n- **Affected Default Docker Configurations:**  \n  - https://github.com/nocobase/nocobase/blob/main/docker/app-mysql/docker-compose.yml#L13  \n  - https://github.com/nocobase/nocobase/blob/main/docker/app-mariadb/docker-compose.yml#L13  \n  - https://github.com/nocobase/nocobase/blob/main/docker/app-postgres/docker-compose.yml#L11  \n  - https://github.com/nocobase/nocobase/blob/main/docker/app-sqlite/docker-compose.yml#L11  \n\n- **Official Deployment Documentation:**  \n  - https://docs.nocobase.com/welcome/getting-started/installation/docker-compose  \n  - https://v2.docs.nocobase.com/get-started/installation/docker",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@nocobase/auth"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.9.0"
      }, {
        "fixed" : "1.9.23"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.9.21"
    }
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@nocobase/auth"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.9.0-beta.18"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.9.0-beta.17"
    }
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@nocobase/auth"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0-alpha.1"
      }, {
        "fixed" : "2.0.0-alpha.52"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2.0.0-alpha.51"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/nocobase/nocobase/security/advisories/GHSA-mv7p-34fv-4874"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-13877"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nocobase/nocobase/commit/de4292ea7847dd26c6306445091769f8b9ee96d5"
  }, {
    "type" : "WEB",
    "url" : "https://docs.nocobase.com/welcome/getting-started/installation/docker-compose"
  }, {
    "type" : "WEB",
    "url" : "https://gist.github.com/H2u8s/f3ede60d7ecfe598ae452aa5a8fbb90d"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/nocobase/nocobase"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nocobase/nocobase/blob/main/docker/app-mariadb/docker-compose.yml#L13"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nocobase/nocobase/blob/main/docker/app-mysql/docker-compose.yml#L13"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nocobase/nocobase/blob/main/docker/app-postgres/docker-compose.yml#L11"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nocobase/nocobase/blob/main/docker/app-sqlite/docker-compose.yml#L11"
  }, {
    "type" : "WEB",
    "url" : "https://v2.docs.nocobase.com/get-started/installation/docker"
  }, {
    "type" : "WEB",
    "url" : "https://vuldb.com/?ctiid.334033"
  }, {
    "type" : "WEB",
    "url" : "https://vuldb.com/?id.334033"
  }, {
    "type" : "WEB",
    "url" : "https://vuldb.com/?submit.692205"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1320", "CWE-321" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-12-09T17:42:53Z",
    "nvd_published_at" : null
  }
}