CVE-2026-25050
mediumpriority · track · 31EPSS 0.004 · 34 %ileexploit · PoCEUUSEPSS · scored 2026-10-27
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–medium · 2.7–5.5
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
exploits (1)
Public proof-of-concept and weaponised exploit code.
affected products (3)
Products and version ranges known to be affected.
advisories (1)
Vendor and ecosystem advisories describing this.
- GHSA-6f65-4fv2-wwchVendure vulnerable to timing attack that enables user enumeration in NativeAuthenticationStrategy2026-01-30ghsa · osvUS
### 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: ```typescript 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.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (8)
External citations — patches, advisories, analysis.
- https://access.redhat.com/security/cve/cve-2026-25050cnnvd
- https://github.com/vendurehq/vendure/releasesPatchcnnvd
- https://github.com/vendurehq/vendure/releases/tag/v3.5.3cnnvd
- https://github.com/vendurehq/vendure/security/advisories/GHSA-6f65-4fv2-wwchcnnvd
- https://github.com/vendurehq/vendure/releases/tag/v3.5.3enisa_euvd
- https://github.com/vendurehq/vendure/security/advisories/GHSA-6f65-4fv2-wwchenisa_euvd
- https://github.com/vendurehq/vendure/releases/tag/v3.5.3ProductRelease Notesnvd
- https://github.com/vendurehq/vendure/security/advisories/GHSA-6f65-4fv2-wwchMitigationVendor Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan