Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-jvf5-q4h5-2jmj

CRITICAL

GHSA-jvf5-q4h5-2jmj is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in madlib-object-utils. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-jvf5-q4h5-2jmj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Prototype Pollution in madlib-object-utils

Also known asCVE-2020-7701SNYK-JS-MADLIBOBJECTUTILS-598676
Published
May 6, 2021
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
1 known

Blast Radius

1 pkg affected
📦madlib-object-utils

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

madlib-object-utils before 0.1.7 is vulnerable to Prototype Pollution via setValue.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmmadlib-object-utilsall versions0.1.7
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 madlib-object-utils. 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 madlib-object-utils to 0.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jvf5-q4h5-2jmj 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-jvf5-q4h5-2jmj 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-jvf5-q4h5-2jmj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

madlib-object-utils before 0.1.7 is vulnerable to Prototype Pollution via setValue.
O3 Security · Impact-Aware SCA

Is GHSA-jvf5-q4h5-2jmj in your dependencies?

O3 detects GHSA-jvf5-q4h5-2jmj across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.