Vendure vulnerable to timing attack that enables user enumeration in NativeAuthenticationStrategy

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

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 · score source

EPSS

• CVE-2026-25050: 0.40% estimated exploitation activity in the next 30 days; percentile 34.26 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 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.

Published by the source

30 Jan 2026, 19:35 UTC

Last modified by the source

3 Feb 2026, 03:03 UTC

Source last checked

26 Oct 2026, 12:41 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-6f65-4fv2-wwch

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-6f65-4fv2-wwch

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-25050

Advisory: Vendure vulnerable to timing attack that enables user enumeration in NativeAuthenticationStrategy
IDs: CVE-2026-25050, GHSA-6f65-4fv2-wwch
Record: https://patchnext.com/advisories/cve-2026-25050 (revision 3, source checked 26 Oct 2026, 12:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @vendure/core 3.5.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @vendure/core: affected < 3.5.3; fixed in 3.5.3

## Suggested inspection (read-only)
- `npm ls @vendure/core --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @vendure/core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-6f65-4fv2-wwch (OSV record GHSA-6f65-4fv2-wwch lists affected ranges: npm @vendure/core >=0 <3.5.3 (fixed))
- Verified: https://github.com/advisories/GHSA-6f65-4fv2-wwch (GitHub-reviewed advisory GHSA-6f65-4fv2-wwch lists affected ranges: npm @vendure/core >=0 <3.5.3)

Commands are suggestions: review each one before running it.