bcrypt is a widely used npm package. As of 2026-05-24, there are 1 known vulnerabilities in the OSV database. The latest stable version is 6.0.0. Developers should audit their dependency trees and update to patched versions.
Package Overview
Known Vulnerabilities (1)
| ID | Severity | Score | Affected Versions | Fixed In | Description |
|---|---|---|---|---|---|
| CVE-2020-7689 | MODERATE | 5.0 | 0 to 5.0.0 | 5.0.0 | Integer Overflow or Wraparound and Use of a Broken or Risky Cryptographic Algorithm in bcrypt |
Security Recommendations
- Pin bcrypt to the latest stable version (6.0.0) in your dependency manifest
- Enable automated dependency updates with Dependabot or Renovate
- Run regular vulnerability scans using
npm audit - Review your lock file (.package-lock.json) after every update
- Monitor the OSV database and NIST NVD for new advisories
FAQ
Is bcrypt safe to use?
bcrypt is actively maintained and widely used. As of 2026-05-24, there are 1 known vulnerabilities listed in the OSV database. Most have patches available. Keeping your dependencies updated and running regular security audits significantly reduces risk.
What vulnerabilities does bcrypt have?
The OSV database currently lists 1 vulnerabilities for bcrypt. These range in severity and are detailed in the vulnerability table above. Check the linked advisories for full technical details and remediation guidance.
How do I update bcrypt to fix vulnerabilities?
Run npm update bcrypt or npm install bcrypt@latest to get the newest version. Use npm audit to identify vulnerable dependencies in your project. Enable automated updates with Dependabot or Renovate to stay current.
Using AI-Generated Code with bcrypt?
Our vibe coding security audit checks for misconfigurations, exposed secrets and vulnerable dependencies in AI-generated codebases. If your project uses bcrypt, we can verify it is locked to a safe version and properly configured.
Get a Vibe Coding Security Audit