CVE-2026-25050

The NativeAuthenticationStrategy.authenticate() method is vulnerable to a timing attack that allows attackers to enumerate valid usernames (email addresses).

Details

In packages/core/src/config/auth/native-authentication-strategy.ts, the authenticate method returns immediately if a user is not found:

const user = await this.userService.getUserByEmailAddress(ctx, data.username);
if (!user) {
    return false; // Instant return (~1-5ms)
}
const passwordMatch = await this.verifyUserPassword(ctx, user.id, data.password);
// Password check takes ~200-400ms with bcrypt (12 rounds)

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.

• Attackers can enumerate valid user accounts
• Enables targeted brute-force or phishing attacks
• Information disclosure (account existence)

Kodem intelligence

Perform a dummy bcrypt check when user is not found to ensure consistent response times.

1. What is CVE-2026-25050? CVE-2026-25050 is a low-severity security vulnerability in @vendure/core (npm), affecting versions < 3.5.3. It is fixed in 3.5.3.
2. Which versions of @vendure/core are affected by CVE-2026-25050? @vendure/core (npm) versions < 3.5.3 is affected.
3. Is there a fix for CVE-2026-25050? Yes. CVE-2026-25050 is fixed in 3.5.3. Upgrade to this version or later.
4. Is CVE-2026-25050 exploitable, and should I be worried? Whether CVE-2026-25050 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
5. What actually determines whether CVE-2026-25050 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.
6. How do I fix CVE-2026-25050? Upgrade @vendure/core to 3.5.3 or later.