VulnerabilityPublished 30 Jan 2026

CVE-2026-25050: vendurehq vendure · Exposure of Sensitive Information Through Data Queries

Affects vendurehq vendureSource CVE Database V5

Not known to be exploited · CVSS 2.7 Low : upgrade to 3.5.3 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score

2.7Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.5.3

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: Unreported

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: Unreported: Based on threat intelligence sources each of the following must apply: · No knowledge of publicly available proof-of-concept · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade vendure and vendurehq/vendure to 3.5.3.

Affected software

Product	Affected	Fixed in
vendurehqvendure	Affected <3.5.3	Fixed in 3.5.3
GitHubvendurehq/vendure`pkg:github/vendurehq/vendure`Other threats	Affected <3.5.3	Fixed in 3.5.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The primary mitigation is to upgrade Vendure to version 3.5.3 or later, where the timing attack has been fixed by equalizing response times regardless of user existence. For organizations unable to upgrade immediately, consider implementing application-layer mitigations such as introducing artificial delays on authentication failures to normalize response times, or using rate limiting and IP reputation filtering to reduce the feasibility of timing attacks. Monitoring authentication logs for anomalous patterns indicative of enumeration attempts is recommended. Additionally, enforce strong password policies and multi-factor authentication (MFA) to reduce the impact of username enumeration. Educate users about phishing risks and monitor for phishing campaigns targeting your user base. Finally, ensure that logging and alerting mechanisms are in place to detect suspicious authentication activity.

Description

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.

Impact

For European organizations using vulnerable versions of Vendure, this vulnerability can lead to the exposure of valid usernames, which are often email addresses. While this does not directly compromise passwords or system integrity, it provides attackers with a verified list of user accounts, significantly lowering the barrier for targeted phishing campaigns, credential stuffing attacks, and social engineering. This can result in unauthorized access if users reuse passwords or fall victim to phishing. E-commerce platforms are high-value targets due to the sensitive customer data and financial transactions involved. The exposure of usernames can also damage customer trust and lead to regulatory scrutiny under GDPR, especially if combined with other vulnerabilities or data breaches. The low CVSS score does not diminish the practical risk posed by information disclosure in the context of layered attacks.

CWE-202Exposure of Sensitive Information Through Data Queries (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
When trying to keep information confidential, an attacker can often infer some of the information by using statistics.
Architecture and Design
This is a complex topic. See the for a good discussion of best practices.
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Jan 2026, 15:43 UTC

WeaknessesCWE-202

Technical details

References

Community reviews

Related threats