Store hashed lostPasswordKey in the database#6691
Merged
Merged
Conversation
Store SHA-256 hash of the lost-password key in the database instead of the raw token. The plain key is only sent to the user via email; any later verification re-hashes the supplied value and compares against the stored hash via hash_equals. This limits the blast radius of a database disclosure: a read-only leak of the user table (e.g. via SQL injection or stolen backup) no longer hands the attacker working password-reset tokens.
dtdesign
approved these changes
Jun 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Store SHA-256 hash of the lost-password key in the database instead of the raw token. The plain key is only sent to the user via email; any later verification re-hashes the supplied value and compares against the stored hash via hash_equals.
This limits the blast radius of a database disclosure: a read-only leak of the user table (e.g. via SQL injection or stolen backup) no longer hands the attacker working password-reset tokens.