VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

ajv: vulnerability history, versions and safety

ajv is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 118 releases, from Feb 2022 to Feb 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 M2
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 11 Feb 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ajv vulnerabilities

Vulert verdict on ajv 8.20.0 i

Updated on 22 Oct 2026

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

Package health score 83/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 8.20.0 — unaffected i
  • Vulnerabilities on record 2 over 4 years · 1 in the last year i
  • Latest disclosure 11 Feb 2026 i
  • Highest CVSS 5.6 i
  • With no published fix 0 i
  • Depended on by 245,523 packages i
  • Stars 14,863 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 ajv, 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
8.20.0 24 Apr 2026 none MIT — Details →
6.15.0 23 Apr 2026 M1 MIT Yes Details →
6.14.0 20 Feb 2026 M1 MIT Yes Details →
8.18.0 14 Feb 2026 none MIT — Details →
8.17.1 12 Jul 2024 M1 MIT Yes Details →
8.16.0 04 Jun 2024 M1 MIT Yes Details →
8.15.0 03 Jun 2024 M1 MIT Yes Details →
8.14.0 25 May 2024 M1 MIT Yes Details →
8.13.0 29 Apr 2024 M1 MIT Yes Details →
8.12.0 03 Jan 2023 M1 MIT Yes Details →
8.11.2 13 Nov 2022 M1 MIT Yes Details →
8.11.1 13 Nov 2022 M1 MIT Yes Details →
8.11.0 22 Mar 2022 M1 MIT Yes Details →
8.10.0 04 Feb 2022 M1 MIT Yes Details →
8.9.0 15 Jan 2022 M1 MIT Yes Details →
8.8.2 21 Nov 2021 M1 MIT Yes Details →
8.8.1 16 Nov 2021 M1 MIT Yes Details →
8.8.0 13 Nov 2021 M1 MIT Yes Details →
8.7.1 08 Nov 2021 M1 MIT Yes Details →
8.7.0 08 Nov 2021 M1 MIT Yes Details →
8.6.3 12 Sep 2021 M1 MIT Yes Details →
8.6.2 15 Jul 2021 M1 MIT Yes Details →
8.6.1 04 Jul 2021 M1 MIT Yes Details →
8.6.0 06 Jun 2021 M1 MIT Yes Details →
8.5.0 20 May 2021 M1 MIT Yes Details →
8.4.0 14 May 2021 M1 MIT Yes Details →
8.3.0 09 May 2021 M1 MIT Yes Details →
8.2.0 27 Apr 2021 M1 MIT Yes Details →
8.1.0 11 Apr 2021 M1 MIT Yes Details →
8.0.5 02 Apr 2021 M1 MIT Yes Details →
8.0.4 02 Apr 2021 M1 MIT Yes Details →
8.0.3 01 Apr 2021 M1 MIT Yes Details →
8.0.2 31 Mar 2021 M1 MIT Yes Details →
8.0.1 27 Mar 2021 M1 MIT Yes Details →
8.0.0 27 Mar 2021 M1 MIT Yes Details →
7.2.4 26 Mar 2021 M1 MIT Yes Details →
8.0.0-beta.4 23 Mar 2021 M1 MIT Yes Details →
8.0.0-beta.3 21 Mar 2021 M1 MIT Yes Details →
7.2.3 20 Mar 2021 M1 MIT Yes Details →
7.2.2 20 Mar 2021 M1 MIT Yes Details →
8.0.0-beta.2 16 Mar 2021 M1 MIT Yes Details →
8.0.0-beta.1 15 Mar 2021 M1 MIT Yes Details →
8.0.0-beta.0 13 Mar 2021 M1 MIT Yes Details →
7.2.1 07 Mar 2021 M1 MIT Yes Details →
7.2.0 07 Mar 2021 M1 MIT Yes Details →
7.1.1 17 Feb 2021 M1 MIT Yes Details →
7.1.0 11 Feb 2021 M1 MIT Yes Details →
7.0.4 01 Feb 2021 M1 MIT Yes Details →
7.0.3 02 Jan 2021 M1 MIT Yes Details →
7.0.2 19 Dec 2020 M1 MIT Yes Details →
7.0.1 16 Dec 2020 M1 MIT Yes Details →
7.0.0 15 Dec 2020 M1 MIT Yes Details →
7.0.0-rc.5 14 Dec 2020 M1 MIT Yes Details →
7.0.0-rc.4 14 Dec 2020 M1 MIT Yes Details →
7.0.0-rc.3 14 Dec 2020 M1 MIT Yes Details →
7.0.0-rc.2 13 Dec 2020 M1 MIT Yes Details →
7.0.0-rc.1 09 Dec 2020 M1 MIT Yes Details →
7.0.0-rc.0 06 Dec 2020 M1 MIT Yes Details →
7.0.0-beta.9 02 Dec 2020 M1 MIT Yes Details →
7.0.0-beta.8 29 Nov 2020 M1 MIT Yes Details →
7.0.0-beta.7 22 Nov 2020 M1 MIT Yes Details →
7.0.0-beta.6 16 Nov 2020 M1 MIT Yes Details →
7.0.0-beta.5 15 Nov 2020 M1 MIT Yes Details →
7.0.0-beta.4 10 Nov 2020 M1 MIT Yes Details →
7.0.0-beta.3 05 Nov 2020 M1 MIT Yes Details →
7.0.0-beta.2 24 Oct 2020 M1 MIT Yes Details →
7.0.0-beta.1 10 Oct 2020 M1 MIT Yes Details →
6.12.6 10 Oct 2020 M1 MIT Yes Details →
7.0.0-beta.0 23 Sep 2020 M1 MIT Yes Details →
7.0.0-alpha.1 16 Sep 2020 M1 MIT Yes Details →
7.0.0-alpha.0 15 Sep 2020 M1 MIT Yes Details →
6.12.5 13 Sep 2020 M1 MIT Yes Details →
6.12.4 15 Aug 2020 M1 MIT Yes Details →
6.12.3 04 Jul 2020 M1 MIT Yes Details →
6.12.2 19 Apr 2020 M2 MIT Yes Details →
6.12.1 18 Apr 2020 M2 MIT Yes Details →
6.12.0 22 Feb 2020 M2 MIT Yes Details →
6.11.0 18 Jan 2020 M2 MIT Yes Details →
6.10.2 14 Jul 2019 M2 MIT Yes Details →
6.10.1 06 Jul 2019 M2 MIT Yes Details →
6.10.0 03 Mar 2019 M2 MIT Yes Details →
6.9.2 22 Feb 2019 M2 MIT Yes Details →
6.9.1 10 Feb 2019 M2 MIT Yes Details →
6.9.0 09 Feb 2019 M2 MIT Yes Details →
6.8.1 02 Feb 2019 M2 MIT Yes Details →
6.8.0 02 Feb 2019 M2 MIT Yes Details →
6.7.0 13 Jan 2019 M2 MIT Yes Details →
6.6.2 16 Dec 2018 M2 MIT Yes Details →
6.6.1 29 Nov 2018 M2 MIT Yes Details →
6.6.0 29 Nov 2018 M2 MIT Yes Details →
6.5.5 04 Nov 2018 M2 MIT Yes Details →
6.5.4 23 Sep 2018 M2 MIT Yes Details →
6.5.3 17 Aug 2018 M2 MIT Yes Details →
6.5.2 30 Jun 2018 M2 MIT Yes Details →
6.5.1 10 Jun 2018 M2 MIT Yes Details →
6.5.0 08 May 2018 M2 MIT Yes Details →
6.4.0 25 Mar 2018 M2 MIT Yes Details →
6.3.0 17 Mar 2018 M2 MIT Yes Details →
6.2.1 03 Mar 2018 M2 MIT Yes Details →
6.2.0 26 Feb 2018 M2 MIT Yes Details →
6.1.1 30 Jan 2018 M2 — Yes Details →
6.1.0 26 Jan 2018 M2 — Yes Details →
6.0.1 11 Jan 2018 M2 — Yes Details →
6.0.0 07 Jan 2018 M2 — Yes Details →
5.5.2 16 Dec 2017 M2 — Yes Details →
6.0.0-rc.1 03 Dec 2017 M2 — Yes Details →
5.5.1 02 Dec 2017 M2 — Yes Details →
6.0.0-rc.0 26 Nov 2017 M2 — Yes Details →
5.5.0 24 Nov 2017 M2 — Yes Details →
5.4.0 20 Nov 2017 M2 — Yes Details →
6.0.0-beta.2 12 Nov 2017 M2 — Yes Details →
6.0.0-beta.1 06 Nov 2017 M2 — Yes Details →
6.0.0-beta.0 06 Nov 2017 M2 — Yes Details →
5.3.0 24 Oct 2017 M2 — Yes Details →
5.2.5 24 Oct 2017 M2 — Yes Details →
5.2.4 22 Oct 2017 M2 — Yes Details →
5.2.3 25 Sep 2017 M2 — Yes Details →
5.2.2 10 Jul 2017 M2 — Yes Details →
5.2.1 06 Jul 2017 M2 — Yes Details →
5.2.0 16 Jun 2017 M2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 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 ajv

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-15366: Prototype Pollution in Ajv 5.6 medium 6.12.3 10 Feb 2022
CVE-2025-69873: ajv Package Suffers from ReDoS Vulnerability with $data Option 5.5 medium 8.18.0 11 Feb 2026

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 ajv

Is ajv safe to use?

Vulert records 2 vulnerabilities for ajv 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 ajv's Vulert package health score?

Vulert scores ajv 83/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 ajv affected?

No. 8.20.0, 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 ajv should I use?

8.20.0 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 ajv have?

2 vulnerabilities are recorded for ajv 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 ajv vulnerabilities disclosed?

1 vulnerability was recorded for ajv in the last 12 months, and the oldest entry in this database dates to 10 Feb 2022. 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 ajv 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 ajv for upcoming vulnerabilities?

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