How severe is GHSA-32j9-6qqm-mq9g?

GHSA-32j9-6qqm-mq9g has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-32j9-6qqm-mq9g?

GHSA-32j9-6qqm-mq9g affects the following packages: node-lmdb (npm). Ecosystems affected: npm.

How do I fix GHSA-32j9-6qqm-mq9g?

Update node-lmdb to 0.9.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-32j9-6qqm-mq9g is resolved across your whole dependency graph.

How do I detect GHSA-32j9-6qqm-mq9g in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for node-lmdb. 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.

How do I mitigate GHSA-32j9-6qqm-mq9g if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-32j9-6qqm-mq9g?

O3 pinpoints whether GHSA-32j9-6qqm-mq9g is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-32j9-6qqm-mq9g actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-32j9-6qqm-mq9g, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

When was GHSA-32j9-6qqm-mq9g published, and has it been updated?

GHSA-32j9-6qqm-mq9g was published on March 17, 2022 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-32j9-6qqm-mq9g

HIGHFix: Venemo/node-lmdb@9776010

GHSA-32j9-6qqm-mq9g is a high-severity (CVSS 7.5) vulnerability in node-lmdb. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-32j9-6qqm-mq9g is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Unhandled case in node-lmdb

Also known asCVE-2022-21164SNYK-JS-NODELMDB-2400723

Published

Mar 17, 2022

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Real-World Exposure

1 pkg affected

📦node-lmdb

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

The package node-lmdb before 0.9.7 is 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

Ecosystem	Package	Vulnerable range	Fix
📦npm	`node-lmdb`	all versions	0.9.7

Exploits & PoCs

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

The package node-lmdb before 0.9.7 are vulnerable to Denial of Service (…

snyk.ioNVDMar 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for node-lmdb. 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.
Fix
Update node-lmdb to 0.9.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-32j9-6qqm-mq9g is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-32j9-6qqm-mq9g 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-32j9-6qqm-mq9g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The package node-lmdb before 0.9.7 is 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 GHSA-32j9-6qqm-mq9g in your dependencies?

O3 detects GHSA-32j9-6qqm-mq9g across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works