NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
LOW severity

CVE-2022-21164 — node-lmdb

LOWFix: Venemo/node-lmdb@9776010

CVE-2022-21164 is a low-severity (CVSS 3.7) vulnerability in node-lmdb. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for node-lmdb — see the affected versions and patch details below.

Denial of Service (DoS)

Also known asGHSA-32j9-6qqm-mq9gSNYK-JS-NODELMDB-2400723
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs71th percentile — riskier than 71% of all scored CVEsHighest risk
0.00%0.61%1.21%1.82%0.3%1.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

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.

33other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
node-lmdbnpm
2Kdownloads / week

Description

The package node-lmdb before 0.9.7 are vulnerable to Denial of Service (DoS) when defining a non-invokable ToString value, which will cause a crash during type check.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmnode-lmdball versions0.9.7npm install node-lmdb@0.9.7

Affected Products

1 product · 1 configurations
Application
node-lmdbnode-lmdb_project
< 0.9.7
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for node-lmdb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update node-lmdb to 0.9.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-21164 is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

The package node-lmdb before 0.9.7 are vulnerable to Denial of Service (DoS) when defining a non-invokable ToString value, which will cause a crash during type check.
O3 Security · Impact-Aware SCA

Is CVE-2022-21164 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2022-21164: node-lmdb DoS — Fixed in 0.9.7