# CVE-2026-25050: Vendure vulnerable to timing attack that enables user enumeration in NativeAuthenticationStrategy

> Attackers can enumerate valid user accounts via timing differences in authentication, exposing user existence information.

- **Severity:** Low 2.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jan 2026
- **Updated:** 30 Jan 2026
- **Also known as:** GHSA-6f65-4fv2-wwch

## What is CVE-2026-25050?

CVE-2026-25050 is a low-severity vulnerability in vendurehq vendure, published on 30 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vendure is an open-source headless commerce platform. Prior to version 3.5.3, the `NativeAuthenticationStrategy.authenticate()` method is vulnerable to a timing attack that allows attackers to enumerate valid usernames (email addresses). In `packages/core/src/config/auth/native-authentication-strategy.ts`, the authenticate method returns immediately if a user is not found. The significant timing difference (~200-400ms for bcrypt vs ~1-5ms for DB miss) allows attackers to reliably distinguish between existing and non-existing accounts. Version 3.5.3 fixes the issue.

Weakness: CWE-202 (Exposure of Sensitive Information Through Data Queries)

## Which versions are affected by CVE-2026-25050?

2 open source packages ship an affected version, including @vendure/core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@vendure/core` | npm | All versions | 3.5.3 |
| `@vendure/core` | npm | All versions | 3.5.3 |

Products: Vendure Vendure.

## How do I fix CVE-2026-25050?

Upgrade @vendure/core to 3.5.3 or later.

## Is CVE-2026-25050 being exploited?

There is no known exploitation of CVE-2026-25050 in the wild and no public exploit code.

Public exploit code:

- CVE-2026-25050 – Timing attack PoC enabling user enumeration via GraphQL authentication (github_poc): https://github.com/Christbowel/CVE-2026-25050

## Other vulnerabilities in vendurehq vendure

- [CVE-2022-23065](https://insights.sbomify.com/CVE-2022-23065/): Vendure - XSS via SVG File Upload (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25050 and fix it if it is affected.

What it is: CVE-2026-25050 is a low-severity vulnerability in vendurehq vendure, published on 30 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-25050 in the wild and no public exploit code.

Affected packages and fixed versions:
- @vendure/core (npm): affected all versions; fixed in 3.5.3
- @vendure/core (npm): affected all versions; fixed in 3.5.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25050/ (Markdown: https://insights.sbomify.com/CVE-2026-25050/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25050
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25050
- OSV: https://osv.dev/vulnerability/CVE-2026-25050

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25050/
Summaries are generated and may contain mistakes; the official description above is the record.