CVE-2026-40887

An 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).

The Admin API is also affected, though exploitation there requires authentication.

Affected versions

• @vendure/core < 2.3.4
• @vendure/core >= 3.0.0, < 3.5.7
• @vendure/core >= 3.6.0, < 3.6.2

Note: 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.

Patched versions

• @vendure/core 2.3.4
• @vendure/core 3.5.7
• @vendure/core 3.6.2

Details

In ProductService.findOneBySlug, the request context's languageCode value is interpolated into a SQL CASE expression via a JavaScript template literal:

.addSelect(
    `CASE translation.languageCode WHEN '${ctx.languageCode}' THEN 2 WHEN '${ctx.channel.defaultLanguageCode}' THEN 1 ELSE 0 END`,
    'sort_order',
)

TypeORM has no opportunity to parameterize this value because it is embedded directly into the SQL string before being passed to the query builder.

The 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.

Attack vector

An 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.

Mitigation

Upgrade to a patched version immediately.

If 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:

private getLanguageCode(req: Request, channel: Channel): LanguageCode | undefined {
    const queryLanguageCode = req.query?.languageCode as string | undefined;
    const isValidFormat = queryLanguageCode && /^[a-zA-Z0-9_-]+$/.test(queryLanguageCode);
    return (
        (isValidFormat ? (queryLanguageCode as LanguageCode) : undefined) ??
        channel.defaultLanguageCode ??
        this.configService.defaultLanguageCode
    );
}

This 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.

The patched versions additionally convert the vulnerable SQL interpolation to a parameterized query as defense in depth.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2026-40887 has a CVSS score of 9.1 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.5.7, 3.6.2, 2.3.4); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-40887? CVE-2026-40887 is a critical-severity SQL injection vulnerability in @vendure/core (npm), affecting versions >= 3.0.0, < 3.5.7. It is fixed in 3.5.7, 3.6.2, 2.3.4. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
2. How severe is CVE-2026-40887? CVE-2026-40887 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @vendure/core are affected by CVE-2026-40887? @vendure/core (npm) versions >= 3.0.0, < 3.5.7 is affected.
4. Is there a fix for CVE-2026-40887? Yes. CVE-2026-40887 is fixed in 3.5.7, 3.6.2, 2.3.4. Upgrade to this version or later.
5. Is CVE-2026-40887 exploitable, and should I be worried? Whether CVE-2026-40887 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-40887 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-40887?
   • Upgrade @vendure/core to 3.5.7 or later
   • Upgrade @vendure/core to 3.6.2 or later
   • Upgrade @vendure/core to 2.3.4 or later