Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

GHSA-5wg4-74h6-q47v

MEDIUMFix: kelektiv/node.bcrypt.js#806

GHSA-5wg4-74h6-q47v is a medium-severity (CVSS 5.9) CWE-190 vulnerability in bcrypt. O3 Security confirms whether GHSA-5wg4-74h6-q47v is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Integer Overflow or Wraparound and Use of a Broken or Risky Cryptographic Algorithm in bcrypt

Also known asCVE-2020-7689SNYK-JS-BCRYPT-572911
Published
Aug 20, 2020
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Jul 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

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.

8Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
bcryptnpm
5.9Mdownloads / week

Description

In bcrypt (npm package) before version 5.0.0, data is truncated wrong when its length is greater than 255 bytes.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmbcryptall versions5.0.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bcrypt. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update bcrypt to 5.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5wg4-74h6-q47v is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-5wg4-74h6-q47v is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-5wg4-74h6-q47v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In bcrypt (npm package) before version 5.0.0, data is truncated wrong when its length is greater than 255 bytes.
O3 Security · Impact-Aware SCA

Is GHSA-5wg4-74h6-q47v in your dependencies?

O3 detects GHSA-5wg4-74h6-q47v across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-5wg4-74h6-q47v: bcrypt (Medium 5.9) | O3 Security