VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

jsondiffpatch: vulnerability history, versions and safety

jsondiffpatch is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 68 releases, from Sep 2025 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 16 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all jsondiffpatch vulnerabilities

Vulert verdict on jsondiffpatch 0.7.6 i

Updated on 23 Oct 2026

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

Package health score 75/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 0.7.6 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 1 in the last year i
  • Latest disclosure 16 May 2026 i
  • Highest CVSS 8.2 i
  • With no published fix 0 i
  • Depended on by 257 packages i
  • Stars 5,349 i
  • OpenSSF scorecard 3/10 i
  • Last release 5 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 jsondiffpatch, 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
0.7.6 14 May 2026 none MIT — Details →
0.7.5 14 May 2026 H1 MIT Yes Details →
0.7.3 31 Mar 2025 H1 MIT Yes Details →
0.7.2 28 Mar 2025 H1 MIT Yes Details →
0.6.2 23 Mar 2025 H1 L1 MIT Yes Details →
0.6.1 21 Mar 2025 H1 L1 MIT Yes Details →
0.6.0 15 Dec 2023 H1 L1 MIT Yes Details →
0.5.0 20 Aug 2023 H1 L1 MIT Yes Details →
0.4.1 02 Jan 2020 H1 L1 MIT Yes Details →
0.4.0 02 Jan 2020 H1 L1 MIT Yes Details →
0.3.11 25 Jun 2018 H1 L1 MIT Yes Details →
0.3.10 13 May 2018 H1 L1 MIT Yes Details →
0.3.9 09 Apr 2018 H1 L1 MIT Yes Details →
0.3.8 29 Mar 2018 H1 L1 MIT Yes Details →
0.3.7 11 Mar 2018 H1 L1 MIT Yes Details →
0.3.6 11 Mar 2018 H1 L1 MIT Yes Details →
0.3.5 14 Feb 2018 H1 L1 MIT Yes Details →
0.3.4 14 Feb 2018 H1 L1 MIT Yes Details →
0.3.3 14 Feb 2018 H1 L1 MIT Yes Details →
0.3.2 11 Feb 2018 H1 L1 MIT Yes Details →
0.3.1 11 Feb 2018 H1 L1 MIT Yes Details →
0.2.5 18 Oct 2017 H1 L1 MIT Yes Details →
0.2.4 12 Sep 2016 H1 L1 MIT Yes Details →
0.2.3 03 Sep 2016 H1 L1 MIT Yes Details →
0.2.2 03 Sep 2016 H1 L1 MIT Yes Details →
0.1.43 01 Apr 2016 H1 L1 MIT Yes Details →
0.1.41 14 Feb 2016 H1 L1 MIT Yes Details →
0.1.40 14 Feb 2016 H1 L1 MIT Yes Details →
0.1.39 14 Feb 2016 H1 L1 MIT Yes Details →
0.1.38 10 Dec 2015 H1 L1 MIT Yes Details →
0.1.37 10 Sep 2015 H1 L1 MIT Yes Details →
0.1.36 05 Sep 2015 H1 L1 MIT Yes Details →
0.1.34 04 Sep 2015 H1 L1 MIT Yes Details →
0.1.33 22 Jun 2015 H1 L1 MIT Yes Details →
0.1.32 22 Jun 2015 H1 L1 MIT Yes Details →
0.1.31 02 Mar 2015 H1 L1 MIT Yes Details →
0.1.27 24 Dec 2014 H1 L1 MIT Yes Details →
0.1.26 22 Dec 2014 H1 L1 MIT Yes Details →
0.1.25 15 Dec 2014 H1 L1 MIT Yes Details →
0.1.24 12 Dec 2014 H1 L1 MIT Yes Details →
0.1.23 12 Dec 2014 H1 L1 MIT Yes Details →
0.1.22 04 Dec 2014 H1 L1 MIT Yes Details →
0.1.21 04 Dec 2014 H1 L1 MIT Yes Details →
0.1.20 02 Nov 2014 H1 L1 MIT Yes Details →
0.1.18 30 Oct 2014 H1 L1 MIT Yes Details →
0.1.17 24 Sep 2014 H1 L1 MIT Yes Details →
0.1.16 24 Sep 2014 H1 L1 MIT Yes Details →
0.1.15 24 Sep 2014 H1 L1 MIT Yes Details →
0.1.14 24 Sep 2014 H1 L1 MIT Yes Details →
0.1.12 24 Sep 2014 H1 L1 MIT Yes Details →
0.1.10 24 Sep 2014 H1 L1 MIT Yes Details →
0.1.8 10 Jul 2014 H1 L1 MIT Yes Details →
0.1.7 10 Jun 2014 H1 L1 MIT Yes Details →
0.1.6 30 May 2014 H1 L1 MIT Yes Details →
0.1.5 05 Mar 2014 H1 L1 MIT Yes Details →
0.1.4 03 Mar 2014 H1 L1 MIT Yes Details →
0.1.3 02 Mar 2014 H1 L1 MIT Yes Details →
0.1.2 02 Mar 2014 H1 L1 MIT Yes Details →
0.1.1 02 Mar 2014 H1 L1 MIT Yes Details →
0.1.0 02 Mar 2014 H1 L1 MIT Yes Details →
0.0.11 24 Jan 2014 H1 L1 MIT Yes Details →
0.0.10 23 Jan 2014 H1 L1 MIT Yes Details →
0.0.9 19 Jan 2014 H1 L1 MIT Yes Details →
0.0.8 16 Jul 2013 H1 L1 MIT Yes Details →
0.0.7 07 Feb 2013 H1 L1 MIT Yes Details →
0.0.5 18 Jul 2012 H1 L1 MIT Yes Details →
0.0.3 18 Jul 2012 H1 L1 MIT Yes Details →
0.0.2 18 Jul 2012 H1 L1 MIT Yes Details →
0.0.1 17 Jul 2012 H1 L1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for jsondiffpatch

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-8657: jsondiffpatch Prototype Pollution Vulnerability 8.2 high 0.7.6 16 May 2026
CVE-2025-9910: jsondiffpatch Vulnerable to Cross-site Scripting (XSS) 4.7 low 0.7.2 11 Sep 2025

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 jsondiffpatch

Is jsondiffpatch safe to use?

Vulert records 2 vulnerabilities for jsondiffpatch in npm: 0 critical, 1 high, 0 medium and 1 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 jsondiffpatch's Vulert package health score?

Vulert scores jsondiffpatch 75/100, which reads as in good shape. 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).

Is the latest version of jsondiffpatch affected?

No. 0.7.6, 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 jsondiffpatch should I use?

0.7.6 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 jsondiffpatch have?

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

How often are new jsondiffpatch vulnerabilities disclosed?

1 vulnerability was recorded for jsondiffpatch in the last 12 months, and the oldest entry in this database dates to 11 Sep 2025. 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 jsondiffpatch 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 jsondiffpatch for upcoming vulnerabilities?

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