CVE-2026-40887: @vendure/core SQL Injection Vulnerability
CRITICALCVE-2026-40887 is a CRITICAL (CVSS 9.1) sql injection vulnerability (CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')) affecting @vendure/core libraries in the npm ecosystem. The issue involves @vendure/core has a sql injection vulnerability. Remediation is available by upgrading affected packages to version 3.5.7, 3.6.2, 2.3.4.
CVE-2026-40887 at a Glance
Security Impact
CVSS: 9.1
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:H/I:N/A:H).
How to Fix CVE-2026-40887
To remediate this vulnerability, upgrade all affected @vendure/core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @vendure/core@3.5.7
npm install @vendure/core@3.6.2
npm install @vendure/core@2.3.4
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-40887, inspect your project dependencies using npm:
npm ls @vendure/core
Analyze the terminal output to locate any version of @vendure/core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.5.7), 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-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'), where the product constructs all or part of an sql command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended sql command when it is sent to a downstream component. without sufficient removal or quoting of sql syntax in user-controllable inputs, the generated sql query can cause those inputs to be interpreted as sql instead of ordinary user data. In @vendure/core, 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
CVE-2026-40887 Affected @vendure/core Versions
3 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@vendure/core
|
npm |
≥ 3.0.0
< 3.5.7
|
3.5.7
|
|
@vendure/core
|
npm |
≥ 3.6.0
< 3.6.2
|
3.6.2
|
|
@vendure/core
|
npm |
≥ 1.7.4
< 2.3.4
|
2.3.4
|
References
Frequently Asked Questions
What is CVE-2026-40887?
Which @vendure/core versions are affected?
What version fixes CVE-2026-40887?
Is @vendure/core affected?
What is the CVSS score of CVE-2026-40887?
What CWE is associated with CVE-2026-40887?
How can I check npm dependencies for CVE-2026-40887?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-9pp3-53p2-ww9v",
"modified" : "2026-04-24T21:10:15Z",
"published" : "2026-04-14T22:38:01Z",
"aliases" : [ "CVE-2026-40887" ],
"summary" : "@vendure/core has a SQL Injection vulnerability",
"details" : "## Summary\n\nAn unauthenticated SQL injection vulnerability exists in the Vendure Shop API. A user-controlled query string parameter is interpolated directly into a raw SQL expression without parameterization or validation, allowing an attacker to execute arbitrary SQL against the database. This affects all supported database backends (PostgreSQL, MySQL/MariaDB, SQLite).\n\nThe Admin API is also affected, though exploitation there requires authentication.\n\n## Affected versions\n\n- `@vendure/core` < 2.3.4\n- `@vendure/core` >= 3.0.0, < 3.5.7\n- `@vendure/core` >= 3.6.0, < 3.6.2\n\nNote: versions 2.3.4 and above in the 2.x line are patched. There were no 2.4.x or 2.x releases between 2.3.x and 3.0.0.\n\n## Patched versions\n\n- `@vendure/core` 2.3.4\n- `@vendure/core` 3.5.7\n- `@vendure/core` 3.6.2\n\n## Details\n\nIn `ProductService.findOneBySlug`, the request context's `languageCode` value is interpolated into a SQL `CASE` expression via a JavaScript template literal:\n\n```ts\n.addSelect(\n `CASE translation.languageCode WHEN '${ctx.languageCode}' THEN 2 WHEN '${ctx.channel.defaultLanguageCode}' THEN 1 ELSE 0 END`,\n 'sort_order',\n)\n```\n\nTypeORM has no opportunity to parameterize this value because it is embedded directly into the SQL string before being passed to the query builder.\n\nThe `languageCode` value can originate from the HTTP query string and is set on the request context for every incoming API request. The value is cast to the `LanguageCode` TypeScript type at compile time, but no runtime validation is performed -- the raw query string value is used as-is.\n\n## Attack vector\n\nAn unauthenticated attacker can append a crafted `languageCode` query parameter to any Shop API request to inject arbitrary SQL into the query. No user interaction is required. The vulnerable endpoint is exposed on every default Vendure installation.\n\n## Mitigation\n\n**Upgrade to a patched version immediately.**\n\nIf you cannot upgrade right away, apply the following hotfix to `RequestContextService.getLanguageCode` to validate the `languageCode` input at the boundary. This blocks injection payloads before they can reach any query:\n\n```ts\nprivate getLanguageCode(req: Request, channel: Channel): LanguageCode | undefined {\n const queryLanguageCode = req.query?.languageCode as string | undefined;\n const isValidFormat = queryLanguageCode && /^[a-zA-Z0-9_-]+$/.test(queryLanguageCode);\n return (\n (isValidFormat ? (queryLanguageCode as LanguageCode) : undefined) ??\n channel.defaultLanguageCode ??\n this.configService.defaultLanguageCode\n );\n}\n```\n\nThis replaces the existing `getLanguageCode` method in `packages/core/src/service/helpers/request-context/request-context.service.ts`. Invalid values are silently dropped and the channel's default language is used instead.\n\nThe patched versions additionally convert the vulnerable SQL interpolation to a parameterized query as defense in depth.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@vendure/core"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "3.0.0"
}, {
"fixed" : "3.5.7"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "@vendure/core"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "3.6.0"
}, {
"fixed" : "3.6.2"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "@vendure/core"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.7.4"
}, {
"fixed" : "2.3.4"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/vendurehq/vendure/security/advisories/GHSA-9pp3-53p2-ww9v"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-40887"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/vendurehq/vendure"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-89" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2026-04-14T22:38:01Z",
"nvd_published_at" : "2026-04-21T20:17:02Z"
}
}