VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

jsoneditor: vulnerability history, versions and safety

jsoneditor is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 84 releases, from Sep 2021 to Oct 2021. 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 M2
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 jsoneditor vulnerabilities

Vulert verdict on jsoneditor 10.4.3 i

Updated on 22 Oct 2026

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

Package health score 80/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 10.4.3 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 12 Oct 2021 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Depended on by 96 packages i
  • Stars 12,265 i
  • OpenSSF scorecard 3/10 i
  • Last release 6 months ago i
  • Licence Apache-2.0 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 jsoneditor, 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
10.4.3 01 Apr 2026 none Apache-2.0 — Details →
10.4.2 15 Oct 2025 none Apache-2.0 — Details →
10.4.1 28 Aug 2025 none Apache-2.0 — Details →
10.4.0 22 Aug 2025 none Apache-2.0 — Details →
10.3.0 01 Aug 2025 none Apache-2.0 — Details →
10.2.0 28 Mar 2025 none Apache-2.0 — Details →
10.1.3 17 Feb 2025 none Apache-2.0 — Details →
10.1.2 18 Dec 2024 none Apache-2.0 — Details →
10.1.1 13 Nov 2024 none Apache-2.0 — Details →
10.1.0 19 Jun 2024 none Apache-2.0 — Details →
10.0.3 25 Apr 2024 none Apache-2.0 — Details →
10.0.2 18 Mar 2024 none Apache-2.0 — Details →
10.0.1 09 Feb 2024 none Apache-2.0 — Details →
10.0.0 21 Dec 2023 none Apache-2.0 — Details →
9.10.5 21 Dec 2023 none Apache-2.0 — Details →
9.10.4 08 Nov 2023 none Apache-2.0 — Details →
9.10.3 21 Sep 2023 none Apache-2.0 — Details →
9.10.2 15 May 2023 none Apache-2.0 — Details →
9.10.1 12 May 2023 none Apache-2.0 — Details →
9.10.0 20 Feb 2023 none Apache-2.0 — Details →
9.9.2 20 Sep 2022 none Apache-2.0 — Details →
9.9.1 19 Sep 2022 none Apache-2.0 — Details →
9.9.0 13 Jun 2022 none Apache-2.0 — Details →
9.8.0 31 May 2022 none Apache-2.0 — Details →
9.7.4 15 Mar 2022 none Apache-2.0 — Details →
9.7.3 04 Mar 2022 none Apache-2.0 — Details →
9.7.2 09 Feb 2022 none Apache-2.0 — Details →
9.7.1 09 Feb 2022 none Apache-2.0 — Details →
9.7.0 30 Jan 2022 none Apache-2.0 — Details →
9.6.0 13 Jan 2022 none Apache-2.0 — Details →
9.5.11 29 Dec 2021 none Apache-2.0 — Details →
9.5.10 27 Dec 2021 none Apache-2.0 — Details →
9.5.9 22 Dec 2021 none Apache-2.0 — Details →
9.5.8 19 Dec 2021 none Apache-2.0 — Details →
9.5.7 06 Nov 2021 none Apache-2.0 — Details →
9.5.6 22 Sep 2021 none Apache-2.0 — Details →
9.5.5 01 Sep 2021 M1 Apache-2.0 Yes Details →
9.5.4 25 Aug 2021 M1 Apache-2.0 Yes Details →
9.5.3 28 Jul 2021 M1 Apache-2.0 Yes Details →
9.5.2 22 Jul 2021 M1 Apache-2.0 Yes Details →
9.5.1 30 Jun 2021 M1 Apache-2.0 Yes Details →
9.5.0 05 Jun 2021 M1 Apache-2.0 Yes Details →
9.4.2 02 Jun 2021 M1 Apache-2.0 Yes Details →
9.4.1 25 Apr 2021 M1 Apache-2.0 Yes Details →
9.4.0 17 Apr 2021 M1 Apache-2.0 Yes Details →
9.3.1 10 Apr 2021 M1 Apache-2.0 Yes Details →
9.3.0 01 Apr 2021 M1 Apache-2.0 Yes Details →
9.2.0 24 Feb 2021 M1 Apache-2.0 Yes Details →
9.1.10 14 Feb 2021 M1 Apache-2.0 Yes Details →
9.1.9 23 Jan 2021 M1 Apache-2.0 Yes Details →
9.1.8 16 Jan 2021 M1 Apache-2.0 Yes Details →
9.1.7 30 Dec 2020 M1 Apache-2.0 Yes Details →
9.1.6 23 Dec 2020 M1 Apache-2.0 Yes Details →
9.1.5 14 Dec 2020 M1 Apache-2.0 Yes Details →
9.1.4 23 Nov 2020 M1 Apache-2.0 Yes Details →
9.1.3 19 Nov 2020 M1 Apache-2.0 Yes Details →
9.1.2 07 Nov 2020 M1 Apache-2.0 Yes Details →
9.1.1 23 Sep 2020 M1 Apache-2.0 Yes Details →
9.1.0 15 Sep 2020 M1 Apache-2.0 Yes Details →
9.0.5 09 Sep 2020 M1 Apache-2.0 Yes Details →
9.0.4 15 Aug 2020 M1 Apache-2.0 Yes Details →
9.0.3 02 Jul 2020 M1 Apache-2.0 Yes Details →
9.0.2 01 Jul 2020 M1 Apache-2.0 Yes Details →
9.0.1 24 Jun 2020 M2 Apache-2.0 Yes Details →
9.0.0 24 May 2020 M2 Apache-2.0 Yes Details →
8.6.8 13 May 2020 M2 Apache-2.0 Yes Details →
8.6.7 10 May 2020 M2 Apache-2.0 Yes Details →
8.6.6 22 Apr 2020 M2 Apache-2.0 Yes Details →
8.6.5 19 Apr 2020 M2 Apache-2.0 Yes Details →
8.6.4 29 Mar 2020 M2 Apache-2.0 Yes Details →
8.6.3 18 Mar 2020 M2 Apache-2.0 Yes Details →
8.6.2 18 Mar 2020 M2 Apache-2.0 Yes Details →
8.6.1 17 Feb 2020 M2 Apache-2.0 Yes Details →
8.6.0 16 Feb 2020 M2 Apache-2.0 Yes Details →
8.5.3 06 Feb 2020 M2 Apache-2.0 Yes Details →
8.5.2 05 Feb 2020 M2 Apache-2.0 Yes Details →
8.5.1 05 Feb 2020 M2 Apache-2.0 Yes Details →
8.5.0 05 Feb 2020 M2 Apache-2.0 Yes Details →
8.4.1 25 Jan 2020 M2 Apache-2.0 Yes Details →
8.4.0 25 Jan 2020 M2 Apache-2.0 Yes Details →
8.3.0 18 Jan 2020 M2 Apache-2.0 Yes Details →
8.2.1 18 Jan 2020 M2 Apache-2.0 Yes Details →
8.2.0 16 Jan 2020 M2 Apache-2.0 Yes Details →
8.1.2 06 Jan 2020 M2 Apache-2.0 Yes Details →
8.1.1 28 Dec 2019 M2 Apache-2.0 Yes Details →
8.1.0 18 Dec 2019 M2 Apache-2.0 Yes Details →
8.0.0 11 Dec 2019 M2 Apache-2.0 Yes Details →
7.5.0 08 Dec 2019 M2 Apache-2.0 Yes Details →
7.4.0 01 Dec 2019 M2 Apache-2.0 Yes Details →
7.3.1 01 Dec 2019 M2 Apache-2.0 Yes Details →
7.3.0 27 Nov 2019 M2 Apache-2.0 Yes Details →
7.2.1 27 Oct 2019 M2 Apache-2.0 Yes Details →
7.2.0 23 Oct 2019 M2 Apache-2.0 Yes Details →
7.1.0 13 Oct 2019 M2 Apache-2.0 Yes Details →
7.0.5 06 Oct 2019 M2 Apache-2.0 Yes Details →
7.0.4 11 Sep 2019 M2 Apache-2.0 Yes Details →
7.0.3 04 Sep 2019 M2 Apache-2.0 Yes Details →
7.0.2 02 Sep 2019 M2 Apache-2.0 Yes Details →
7.0.1 01 Sep 2019 M2 Apache-2.0 Yes Details →
7.0.0 01 Sep 2019 M2 Apache-2.0 Yes Details →
6.4.1 28 Aug 2019 M2 — Yes Details →
6.4.0 28 Aug 2019 M2 — Yes Details →
6.3.0 15 Aug 2019 M2 — Yes Details →
6.2.1 01 Aug 2019 M2 — Yes Details →
6.2.0 28 Jul 2019 M2 — Yes Details →
6.1.0 22 Jun 2019 M2 — Yes Details →
6.0.0 12 Jun 2019 M2 — Yes Details →
5.34.0 08 Jun 2019 M2 — Yes Details →
5.33.0 29 May 2019 M2 — Yes Details →
5.32.5 27 Apr 2019 M2 — Yes Details →
5.32.4 10 Apr 2019 M2 — Yes Details →
5.32.3 04 Apr 2019 M2 — Yes Details →
5.32.2 03 Apr 2019 M2 — Yes Details →
5.32.1 28 Mar 2019 M2 — Yes Details →
5.32.0 20 Mar 2019 M2 — Yes Details →
5.31.1 14 Mar 2019 M2 — Yes Details →
5.31.0 10 Mar 2019 M2 — Yes Details →
5.30.0 02 Mar 2019 M2 — Yes Details →
5.29.1 20 Feb 2019 M2 — Yes Details →
5.29.0 16 Feb 2019 M2 — Yes Details →

The newest 120 of 218 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2

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

03 Vulnerabilities

Recorded vulnerabilities for jsoneditor

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-23849: Cross-site Scripting in jsoneditor 6.1 medium 9.0.2 12 Oct 2021
CVE-2021-3822: Regular Expression Denial of Service in jsoneditor 5.3 medium 9.5.6 29 Sep 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: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 jsoneditor

Is jsoneditor safe to use?

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

Vulert scores jsoneditor 80/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 jsoneditor affected?

No. 10.4.3, 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 jsoneditor should I use?

10.4.3 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 jsoneditor have?

2 vulnerabilities are recorded for jsoneditor in the npm ecosystem: 0 critical, 0 high, 2 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 jsoneditor vulnerabilities disclosed?

0 vulnerabilities were recorded for jsoneditor in the last 12 months, and the oldest entry in this database dates to 29 Sep 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 jsoneditor 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 jsoneditor for upcoming vulnerabilities?

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