Authentication Weakness in keystone
Summary
GHSA-9xgp-hfw7-73rq: Authentication Weakness in keystone. Affects keystone versions < 0.3.16. Fixed in 0.3.16. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Keystone is an npm package that provides authentication functionality. It allows users to sign in using their email address and password. However, a vulnerability has been discovered in versions prior to 0.3.16 that allows incomplete email addresses to be matched during the sign-in process. While a correct password is still required, this weakness could potentially lead to unauthorized access to user accounts.
Vulnerability Detail
The vulnerability in keystone arises from a bug in the default sign-in functionality. Incomplete email addresses can be matched, allowing an attacker to potentially guess the complete email address and gain unauthorized access to an account by providing the correct password. This vulnerability has a moderate severity rating and has been reviewed by GitHub. No Common Weakness Enumeration (CWE) IDs have been associated with this vulnerability.
How To Fix
Latest published version: 4.2.1 as of 22 Oct 2026
npm install keystone@4.2.1
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
0.3.16
This is the first release that contains the fix.
npm install keystone@0.3.16
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Conclusion
In conclusion, the keystone package prior to version 0.3.16 has an authentication weakness that allows incomplete email addresses to be matched during sign-in. This could potentially lead to unauthorized access to user accounts. It is recommended to upgrade to version 0.3.16 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for keystone →
FAQ
The vulnerability allows incomplete email addresses to be matched during the sign-in process, potentially leading to unauthorized access to user accounts.
Versions of keystone prior to 0.3.16 are affected by this vulnerability.
Yes, a correct password is still required to complete the sign-in process.
Yes, this vulnerability has been reviewed by GitHub.
No, there are no CWE IDs associated with this vulnerability.
References
Related vulnerabilities
Recent vulnerabilities recorded for keystone.