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

CVE-2021-23807

CRITICALFix: janl/node-jsonpointer@a0345f3

CVE-2021-23807 is a critical-severity (CVSS 9.8) CWE-843 vulnerability in jsonpointer. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2021-23807 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Prototype Pollution in node-jsonpointer

Also known asGHSA-282f-qqgm-c34q
Published
Nov 3, 2021
Updated
Jul 8, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
2 known
Exploitation data as of Jul 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
📦jsonpointer📦org.webjars.npm:json-pointer

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

This affects the package jsonpointer before 5.0.0. A type confusion vulnerability can lead to a bypass of a previous Prototype Pollution fix when the pointer components are arrays.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmjsonpointerall versions5.0.0
📦npmorg.webjars.npm:json-pointerall versions5.0.0
Exploits & PoCs
2

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 jsonpointer. 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 jsonpointer to 5.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-23807 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 CVE-2021-23807 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 CVE-2021-23807. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

This affects the package jsonpointer before 5.0.0. A type confusion vulnerability can lead to a bypass of a previous Prototype Pollution fix when the pointer components are arrays.
O3 Security · Impact-Aware SCA

Is CVE-2021-23807 in your dependencies?

O3 detects CVE-2021-23807 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

CVE-2021-23807: Prototype Pollution in… | O3 Security