GHSA-h9wq-xcqx-mqxm — @vendure/core
Fix: vendure-ecommerce/vendure@4a10d67GHSA-h9wq-xcqx-mqxm is a security vulnerability in @vendure/core. A fix is available for @vendure/core — see the affected versions and patch details below.
Vendure Cross Site Request Forgery vulnerability impacting all API requests
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
Impact
Vendure is an e-commerce GraphQL framework with a number of APIs and different levels of authorization. By default the Cookie settings are insecure, having the SameSite setting as false which results in not having one (originates from the cookie-session npm package’s default settings).
Patches
In progress
Workarounds
Manually set the authOptions.cookieOptions.sameSite configuration option to 'strict', 'lax' or true.
References
Are there any links users can visit to find out more?
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @vendure/core | all versions | 2.0.3npm install @vendure/core@2.0.3 |
Detection & 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 2.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h9wq-xcqx-mqxm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-h9wq-xcqx-mqxm can be triaged on real exposure rather than presence alone.
Tailored to GHSA-h9wq-xcqx-mqxm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-h9wq-xcqx-mqxm in your dependencies?
O3 Security finds GHSA-h9wq-xcqx-mqxm across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.