GHSA-6f65-4fv2-wwch — @vendure/core
Fix: vendurehq/vendure@7f0c555GHSA-6f65-4fv2-wwch is a CWE-202 vulnerability in @vendure/core. A fix is available for @vendure/core — see the affected versions and patch details below.
Vendure vulnerable to timing attack that enables user enumeration in NativeAuthenticationStrategy
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-6f65-4fv2-wwch.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@vendure/corenpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @vendure/core | all versions | 3.5.3npm install @vendure/core@3.5.3 |
Affected Products
vendurevendureDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @vendure/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @vendure/core to 3.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6f65-4fv2-wwch is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is GHSA-6f65-4fv2-wwch in your dependencies?
Find it across npm, including transitive dependencies.