Loading vulnerability…
Vendure (open-source headless commerce platform) contains a timing side-channel in NativeAuthenticationStrategy.authenticate() (in packages/core/src/config/auth/native-authentication-strategy.ts) prior to version 3.5.3. When a supplied username/email does not exist, the method returns immediately after the database lookup. When the user exists, the code proceeds to bcrypt password verification, introducing a large and consistent response-time difference (~200–400ms for bcrypt vs ~1–5ms for a DB miss). This measurable discrepancy allows an attacker to distinguish valid from invalid usernames and enumerate accounts.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
@vendure/core to version 3.5.3 or later, which fixes the timing discrepancy. A code-level remediation is to ensure constant-time behavior by performing a dummy bcrypt verification (or equivalent constant-time operation) even when the user record is not found, so the authentication path duration is similar regardless of account existence.No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.