{"answers":{"affected":"2 open source packages ship an affected version, including @vendure/core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-25050 in the wild and no public exploit code.","fix":"Upgrade @vendure/core to 3.5.3 or later.","what":"CVE-2026-25050 is a low-severity vulnerability in vendurehq vendure, published on 30 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-25050 and fix it if it is affected.\n\nWhat it is: CVE-2026-25050 is a low-severity vulnerability in vendurehq vendure, published on 30 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-25050 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @vendure/core (npm): affected all versions; fixed in 3.5.3\n- @vendure/core (npm): affected all versions; fixed in 3.5.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-25050/ (Markdown: https://insights.sbomify.com/CVE-2026-25050/index.md)","id":"CVE-2026-25050","markdown":"https://insights.sbomify.com/CVE-2026-25050/index.md","name":"CVE-2026-25050","record":{"aliases":["GHSA-6f65-4fv2-wwch"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Vendure commerce platform","requires_auth":"none","summary":"Attackers can enumerate valid user accounts via timing differences in authentication, exposing user existence information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"vendure","vendor":"vendure"}],"cvss":{"score":2.7,"severity":"low","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-202","name":"Exposure of Sensitive Information Through Data Queries"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2026-02-06","github_poc":1,"max_poc_stars":2,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-02-06T17:24:24Z","kind":"github_poc","ref":"https://github.com/Christbowel/CVE-2026-25050","stars":2,"title":"CVE-2026-25050 – Timing attack PoC enabling user enumeration via GraphQL authentication"}],"tier":"poc_unverified"},"has_fix":true,"headline":"Vendure vulnerable to timing attack that enables user enumeration in NativeAuthenticationStrategy","id":"CVE-2026-25050","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"n8n Improper CSP Enforcement in Webhook Responses May Allow Stored XSS","id":"CVE-2026-25051"},"packages":[{"ecosystem":"npm","fixed":["3.5.3"],"introduced":["0"],"last_affected":[],"package":"@vendure/core","purl":null,"source":"GHSA-6f65-4fv2-wwch"},{"ecosystem":"npm","fixed":["3.5.3"],"introduced":["0"],"last_affected":[],"package":"@vendure/core","purl":"pkg:npm/%40vendure/core","source":"GHSA-6f65-4fv2-wwch"}],"prev":{"headline":"n8n Has an Expression Escape Vulnerability Leading to RCE","id":"CVE-2026-25049"},"products":["vendure"],"published":"2026-01-30","related":[{"cvss_score":5.4,"headline":"Vendure - XSS via SVG File Upload","id":"CVE-2022-23065","kev_date_added":null,"published":"2022-05-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-30","vendors":["vendurehq"]},"summary":"Attackers can enumerate valid user accounts via timing differences in authentication, exposing user existence information.","url":"https://insights.sbomify.com/CVE-2026-25050/"}