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

CVE-2020-7766 — json-ptr

HIGHFix: 418sec/json-ptr#3

CVE-2020-7766 is a high-severity (CVSS 7.3) CWE-1321 vulnerability in json-ptr. 2 public exploit references exist, so weaponization risk is real. A fix is available for json-ptr — see the affected versions and patch details below.

Arbitrary Code Execution in json-ptr

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

EPSS Exploitation Probability

via FIRST.org ↗
1.9%probability of exploitation in next 30 days
Lower Risk+0.84%
Lower risk than most CVEs79th percentile — riskier than 79% of all scored CVEsHighest risk
0.56%1.18%1.79%2.40%1.1%1.9%Jun 26Sep 26

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

How urgent is this, really

CVE-2020-7766 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

json-ptrnpm
3.2Mdownloads / week

Description

npm json-ptr before 2.1.0 has an arbitrary code execution vulnerability. The issue occurs in the set operation when the force flag is set to true. The function recursively set the property in the target object, however it does not properly check the key being set, leading to a prototype pollution.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmjson-ptrall versions2.1.0npm install json-ptr@2.1.0

Affected Products

1 product · 1 configurations
Application
json-ptrjson-ptr_project
< 2.0.0
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.

This affects all versions of package json-ptr. The issue occurs in the s…

snyk.ioNVDJul 2021

This affects all versions of package json-ptr. The issue occurs in the s…

snyk.ioNVDJul 2021

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-ptr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

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

Frequently Asked Questions

npm `json-ptr` before 2.1.0 has an arbitrary code execution vulnerability. The issue occurs in the [set operation](https://flitbit.github.io/json-ptr/classes/_src_pointer_.jsonpointer.htmlset) when the force flag is set to true. The function recursively set the property in the target object, however it does not properly check the key being set, leading to a prototype pollution.
O3 Security · Impact-Aware SCA

Is CVE-2020-7766 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-7766: json-ptr RCE — Fixed in 2.1.0