NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

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

lowCVSS 4.0 2.7GHSA-6f65-4fv2-wwch

Summary 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: The significant timing difference (~200-400ms for bcrypt vs ~1-5ms for DB miss) allows attackers to reliably…

Published Jan 30, 2026

Affected packages

@vendure/core

Ecosystem
npm
Affected
< 3.5.3
Fixed in
3.5.3
Check
npm ls @vendure/core

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Summary

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.

Impact

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

Recommended Fix

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

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries