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

CVE-2021-23820 — json-pointer

MEDIUMFix: manuelstofer/json-pointer#36

CVE-2021-23820 is a medium-severity (CVSS 5.6) CWE-843 vulnerability in json-pointer. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for json-pointer — see the affected versions and patch details below.

Prototype Pollution in json-pointer

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs80th percentile — riskier than 80% of all scored CVEsHighest risk
0.02%0.81%1.59%2.37%0.5%1.9%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.

441other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
json-pointernpm
6.1Mdownloads / week

Description

This affects versions of package json-pointer up to and including 0.6.1. A type confusion vulnerability can lead to a bypass of CVE-2020-7709 when the pointer components are arrays.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmjson-pointerall versions0.6.2npm install json-pointer@0.6.2

Affected Products

1 product · 1 configurations
Application
json-pointermanuelstofer
< 0.6.2
range
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 json-pointer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update json-pointer to 0.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-23820 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
ProductFixed inAdvisory
RHACS-3.70-RHEL-8advanced-cluster-security/rhacs-collector-slim-rhel8:3.70.0-2RHSA-2022:4880

Frequently Asked Questions

This affects versions of package `json-pointer` up to and including `0.6.1`. A type confusion vulnerability can lead to a bypass of CVE-2020-7709 when the pointer components are arrays.
O3 Security · Impact-Aware SCA

Is CVE-2021-23820 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2021-23820: json-pointer — Fixed in 0.6.2