VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

json-ptr: vulnerability history, versions and safety

json-ptr is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 65 releases, from May 2021 to Nov 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H2 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all json-ptr vulnerabilities

Vulert verdict on json-ptr 3.1.1 i

Updated on 23 Oct 2026

Good news: 3.1.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 45/100
  • Security No known security issues
  • Maintenance Deprecated
  • Popularity Niche
  • Community Quiet

The registry marks the latest release as deprecated, which caps this score.

What to do: Stay on 3.1.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.1.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.1.1 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 08 Nov 2021 i
  • Highest CVSS 7.3 i
  • With no published fix 0 i
  • Depended on by 239 packages i
  • Stars 94 i
  • Last release 51 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for json-ptr, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.1.2-dependabot-npm-and-yarn-webpack-5-76-0.29bfad0 14 Mar 2023 none MIT — Details →
3.1.2-dependabot-npm-and-yarn-json5-2-2-3.c209166 07 Jan 2023 none MIT — Details →
3.1.1 13 Jul 2022 none MIT — Details →
3.1.2-main.1988f05 13 Jul 2022 none MIT — Details →
3.1.1-main.3292abf 13 Jul 2022 none MIT — Details →
3.1.1-dependabot-npm-and-yarn-minimist-1-2-6.98d2cb6 09 Apr 2022 none MIT — Details →
3.1.1-symbols.0e6db58 04 Feb 2022 none MIT — Details →
3.1.1-main.677a678 03 Feb 2022 none MIT — Details →
3.1.1-fix-examples.80a275d 03 Feb 2022 none MIT — Details →
3.1.1-main.02aa710 02 Feb 2022 none MIT — Details →
3.1.0 02 Feb 2022 none MIT — Details →
3.0.2-main.78e4a61 02 Feb 2022 none MIT — Details →
3.0.2-main.1916627 02 Feb 2022 none MIT — Details →
3.0.2-main.e7bd39d 02 Feb 2022 none MIT — Details →
3.0.2-main.afa67f9 02 Feb 2022 none MIT — Details →
3.0.2-main.50697cc 02 Feb 2022 none MIT — Details →
3.0.2-master.50697cc 02 Feb 2022 none MIT — Details →
3.0.2-bug-issue-48.6c9db9f 02 Feb 2022 none MIT — Details →
3.0.2-master.2e0b67f 19 Nov 2021 none MIT — Details →
3.0.2-master.a2e0055 19 Nov 2021 none MIT — Details →
3.0.1 19 Nov 2021 none MIT — Details →
3.0.1-master.cb11e0b 19 Nov 2021 none MIT — Details →
3.0.1-older-nodes.e0918b8 19 Nov 2021 none MIT — Details →
3.0.1-master.55c1dd5 26 Oct 2021 none MIT — Details →
3.0.1-master.2d8c1ab 26 Oct 2021 none MIT — Details →
3.0.0 26 Oct 2021 none MIT — Details →
2.2.1-master.18a4d58 26 Oct 2021 M1 MIT Yes Details →
2.2.1-packaging-rollup.7af30ca 26 Oct 2021 M1 MIT Yes Details →
2.2.1-master.456a172 14 May 2021 M1 MIT Yes Details →
2.2.1-master.0c06aa1 14 May 2021 M1 MIT Yes Details →
2.2.0 14 May 2021 M1 MIT Yes Details →
2.1.3-master.eaf24e6 14 May 2021 M1 MIT Yes Details →
2.1.3-master.4871821 14 May 2021 M1 MIT Yes Details →
2.1.2-relative.f48c5e7 14 May 2021 M1 MIT Yes Details →
2.1.2-relative.3103314 14 May 2021 M1 MIT Yes Details →
2.1.2-relative.03b7b06 13 May 2021 M1 MIT Yes Details →
2.1.3-master.51308ff 13 May 2021 M1 MIT Yes Details →
2.1.2 13 May 2021 M1 MIT Yes Details →
2.1.2-relative.ab59597 13 May 2021 M1 MIT Yes Details →
2.1.2-relative.2485c9e 13 May 2021 M1 MIT Yes Details →
2.1.1 12 May 2021 M1 MIT Yes Details →
2.1.2-master.bdd6317 12 May 2021 M1 MIT Yes Details →
2.1.1-master.98922c7 12 May 2021 M1 MIT Yes Details →
2.1.1-issue-36.f2a3959 12 May 2021 M1 MIT Yes Details →
2.1.1-master.6efd1ec 12 May 2021 M1 MIT Yes Details →
2.1.0 12 May 2021 M1 MIT Yes Details →
2.0.1-master.2539e34 12 May 2021 H2 M1 MIT Yes Details →
2.0.1-issue-28-and-30.f825bd7 11 May 2021 H2 M1 MIT Yes Details →
2.0.1-master.434066d 11 May 2021 H2 M1 MIT Yes Details →
2.0.1-master.bd99031 21 Oct 2020 H2 M1 MIT Yes Details →
2.0.0 21 Oct 2020 H2 M1 MIT Yes Details →
1.3.3-master.f23e2e5 21 Oct 2020 H2 M1 MIT Yes Details →
1.3.3-master.983a133 20 Jul 2020 H2 M1 MIT Yes Details →
1.3.2 20 Jul 2020 H2 M1 MIT Yes Details →
1.3.3-master.10cfb6b 20 Jul 2020 H2 M1 MIT Yes Details →
1.3.2-master.b0d7d5e 19 Jul 2020 H2 M1 MIT Yes Details →
1.3.2-master.4077c81 19 Jul 2020 H2 M1 MIT Yes Details →
1.3.2-master.b8ed3fc 19 Jul 2020 H2 M1 MIT Yes Details →
1.3.2-dependabot-npm-and-yarn-lodash-4-17-19.7fd4b3e 16 Jul 2020 H2 M1 MIT Yes Details →
1.3.1 12 Jul 2020 H2 M1 MIT Yes Details →
1.3.2-master.3531b8f 12 Jul 2020 H2 M1 MIT Yes Details →
1.3.1-master.045068f 12 Jul 2020 H2 M1 MIT Yes Details →
1.3.1-master.ed42d86 12 Jul 2020 H2 M1 MIT Yes Details →
1.3.1-master.b170f35 12 Jul 2020 H2 M1 MIT Yes Details →
1.3.1-master.6759cc9 12 Jul 2020 H2 M1 MIT Yes Details →
1.3.1-master.ef9842c 10 Jul 2020 H2 M1 MIT Yes Details →
1.3.1-master.f714cdc 10 Jul 2020 H2 M1 MIT Yes Details →
1.3.1-master.8983378 10 Jul 2020 H2 M1 MIT Yes Details →
1.3.0 10 Jul 2020 H2 M1 MIT Yes Details →
1.2.1-master.9e1cb86 10 Jul 2020 H2 M1 MIT Yes Details →
1.2.1-ts.cf62f17 10 Jul 2020 H2 M1 MIT Yes Details →
1.2.1-ts.d9366c0 10 Jul 2020 H2 M1 MIT Yes Details →
1.2.1-ts.54cfffa 10 Jul 2020 H2 M1 MIT Yes Details →
1.2.1-ts.eec9b2a.0 10 Jul 2020 H2 M1 MIT Yes Details →
1.2.1-ts.93dc79c.0 10 Jul 2020 H2 M1 MIT Yes Details →
1.2.1-ts.c739a2e.0 28 Mar 2020 H2 M1 MIT Yes Details →
1.2.1-ts.33951c4.0 08 Mar 2020 H2 M1 MIT Yes Details →
1.2.1-ts.64a7978.0 24 Feb 2020 H2 M1 MIT Yes Details →
1.2.0-ts.da6e2a1 17 Feb 2020 H2 M1 MIT Yes Details →
1.2.0-ts.38ea8fe 17 Feb 2020 H2 M1 MIT Yes Details →
1.2.0 14 Sep 2019 H2 M1 MIT Yes Details →
1.1.2 10 Mar 2019 H2 M1 MIT Yes Details →
1.1.1 14 Oct 2018 H2 M1 MIT Yes Details →
1.1.0 24 Feb 2018 H2 M1 MIT Yes Details →
1.0.1 31 Jul 2016 H2 M1 MIT Yes Details →
1.0.0 12 Jan 2016 H2 M1 MIT Yes Details →
0.3.1 04 Jan 2016 H2 M1 MIT Yes Details →
0.3.0 04 Jan 2016 H2 M1 MIT Yes Details →
0.2.0 21 Oct 2014 H2 M1 MIT Yes Details →
0.1.1 02 Oct 2013 H2 M1 MIT Yes Details →
0.1.0 11 Jun 2013 H2 M1 MIT Yes Details →

All 91 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for json-ptr

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-7766: Arbitrary Code Execution in json-ptr 7.3 high 2.1.0 10 May 2021
CVE-2021-23509: Prototype Pollution in json-ptr 5.6 medium 3.0.0 08 Nov 2021
Arbitrary Code Execution in json-ptr N/A high 2.1.0 26 May 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About json-ptr

Is json-ptr safe to use?

Vulert records 3 vulnerabilities for json-ptr in npm: 0 critical, 2 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is json-ptr's Vulert package health score?

Vulert scores json-ptr 45/100, which reads as risky. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The registry marks the latest release as deprecated, which caps this score.

Is the latest version of json-ptr affected?

No. 3.1.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of json-ptr should I use?

3.1.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does json-ptr have?

3 vulnerabilities are recorded for json-ptr in the npm ecosystem: 0 critical, 2 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new json-ptr vulnerabilities disclosed?

0 vulnerabilities were recorded for json-ptr in the last 12 months, and the oldest entry in this database dates to 10 May 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of json-ptr are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor json-ptr for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the json-ptr version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.