VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

joi: vulnerability history, versions and safety

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

i
8 vulnerabilities recorded H2 M2 L4
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
8 in the last 12 months

Most recent disclosure 29 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all joi vulnerabilities

Vulert verdict on joi 18.3.0 i

Updated on 23 Oct 2026

Careful: 18.3.0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

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

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 18.3.0 — affected i
  • Vulnerabilities on record 8 over 1 year · 8 in the last year i
  • Latest disclosure 29 Sep 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 1 i
  • Depended on by 1,175 packages i
  • Stars 21,164 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence BSD-3-Clause 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 joi, 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
18.3.0 16 Oct 2026 H1 BSD-3-Clause No Details →
17.13.8 11 Sep 2026 M1 BSD-3-Clause Yes Details →
18.2.9 11 Sep 2026 H1 BSD-3-Clause No Details →
18.2.8 02 Sep 2026 H1 BSD-3-Clause No Details →
18.2.7 02 Sep 2026 H1 BSD-3-Clause No Details →
17.13.7 02 Sep 2026 M2 BSD-3-Clause Yes Details →
18.2.6 02 Sep 2026 H1 BSD-3-Clause No Details →
17.13.6 19 Aug 2026 H1 M2 BSD-3-Clause Yes Details →
18.2.5 19 Aug 2026 H1 BSD-3-Clause No Details →
17.13.5 19 Aug 2026 H1 M2 L2 BSD-3-Clause Yes Details →
18.2.4 19 Aug 2026 H1 BSD-3-Clause No Details →
18.2.3 17 Jun 2026 H1 BSD-3-Clause No Details →
18.2.2 17 Jun 2026 H1 BSD-3-Clause No Details →
17.13.4 12 Jun 2026 H1 M2 L4 BSD-3-Clause Yes Details →
18.2.1 04 May 2026 H1 BSD-3-Clause No Details →
18.2.0 04 May 2026 H1 M1 BSD-3-Clause No Details →
18.1.2 30 Mar 2026 H1 M1 BSD-3-Clause No Details →
18.1.1 23 Mar 2026 H1 M1 BSD-3-Clause No Details →
18.1.0 23 Mar 2026 H1 M1 BSD-3-Clause No Details →
18.0.2 19 Nov 2025 H1 M1 BSD-3-Clause No Details →
18.0.1 20 Aug 2025 H1 M1 BSD-3-Clause No Details →
18.0.0 03 Aug 2025 H1 M1 BSD-3-Clause No Details →
17.13.3 19 Jun 2024 H1 M2 L4 BSD-3-Clause Yes Details →
17.13.2 19 Jun 2024 H1 M2 L4 BSD-3-Clause Yes Details →
17.13.1 02 May 2024 H1 M2 L4 BSD-3-Clause Yes Details →
17.13.0 23 Apr 2024 H1 M2 L4 BSD-3-Clause Yes Details →
17.12.3 03 Apr 2024 H1 M2 L4 BSD-3-Clause Yes Details →
17.12.2 21 Feb 2024 H1 M2 L4 BSD-3-Clause Yes Details →
17.12.1 29 Jan 2024 H1 M2 L4 BSD-3-Clause Yes Details →
17.12.0 17 Jan 2024 H1 M2 L4 BSD-3-Clause Yes Details →
17.11.1 15 Jan 2024 H1 M2 L4 BSD-3-Clause Yes Details →
12.1.1 01 Jan 2024 M2 non-standard Yes Details →
17.11.0 04 Oct 2023 H1 M2 L4 BSD-3-Clause Yes Details →
17.10.2 17 Sep 2023 H1 M2 L4 BSD-3-Clause Yes Details →
17.10.1 31 Aug 2023 H1 M2 L4 BSD-3-Clause Yes Details →
17.10.0 27 Aug 2023 H1 M2 L4 BSD-3-Clause Yes Details →
17.9.2 24 Apr 2023 H1 M2 L4 BSD-3-Clause Yes Details →
17.9.1 21 Mar 2023 H1 M2 L4 BSD-3-Clause Yes Details →
17.9.0 20 Mar 2023 H1 M2 L4 BSD-3-Clause Yes Details →
17.8.4 14 Mar 2023 H1 M2 L4 BSD-3-Clause Yes Details →
17.8.3 21 Feb 2023 H1 M2 L4 BSD-3-Clause Yes Details →
17.8.2 21 Feb 2023 H1 M2 L4 BSD-3-Clause Yes Details →
17.8.1 19 Feb 2023 H1 M2 L4 BSD-3-Clause Yes Details →
17.8.0 19 Feb 2023 H1 M2 L4 BSD-3-Clause Yes Details →
17.7.1 10 Feb 2023 H1 M2 L4 BSD-3-Clause Yes Details →
17.7.0 01 Nov 2022 H1 M2 L4 BSD-3-Clause Yes Details →
17.6.4 22 Oct 2022 H1 M2 L4 BSD-3-Clause Yes Details →
17.6.3 11 Oct 2022 H1 M2 L4 BSD-3-Clause Yes Details →
17.6.2 29 Sep 2022 H1 M2 L4 BSD-3-Clause Yes Details →
17.6.1 22 Sep 2022 H1 M2 L4 BSD-3-Clause Yes Details →
17.6.0 26 Jan 2022 H1 M2 L4 BSD-3-Clause Yes Details →
17.5.0 02 Dec 2021 H1 M2 L4 BSD-3-Clause Yes Details →
17.4.3 01 Dec 2021 H1 M2 L4 BSD-3-Clause Yes Details →
17.4.2 01 Aug 2021 H1 M2 L4 BSD-3-Clause Yes Details →
17.4.1 11 Jul 2021 H1 M2 L4 BSD-3-Clause Yes Details →
17.4.0 08 Feb 2021 H1 M2 L4 BSD-3-Clause Yes Details →
17.3.0 24 Oct 2020 H1 M2 L4 BSD-3-Clause Yes Details →
17.2.1 19 Aug 2020 H1 M2 L4 BSD-3-Clause Yes Details →
17.2.0 05 Aug 2020 H1 M2 L4 BSD-3-Clause Yes Details →
17.1.1 16 Jul 2020 M2 L2 BSD-3-Clause Yes Details →
14.3.1 28 Dec 2018 M2 BSD-3-Clause Yes Details →
14.3.0 25 Nov 2018 M2 BSD-3-Clause Yes Details →
14.2.0 25 Nov 2018 M2 BSD-3-Clause Yes Details →
14.1.1 24 Nov 2018 M2 BSD-3-Clause Yes Details →
14.1.0 19 Nov 2018 M2 BSD-3-Clause Yes Details →
14.0.6 12 Nov 2018 M2 BSD-3-Clause Yes Details →
14.0.5 11 Nov 2018 M2 BSD-3-Clause Yes Details →
14.0.4 03 Nov 2018 M2 BSD-3-Clause Yes Details →
14.0.3 01 Nov 2018 M2 BSD-3-Clause Yes Details →
14.0.2 29 Oct 2018 M2 BSD-3-Clause Yes Details →
14.0.1 22 Oct 2018 M2 BSD-3-Clause Yes Details →
14.0.0 14 Oct 2018 M2 BSD-3-Clause Yes Details →
13.7.0 29 Sep 2018 M2 BSD-3-Clause Yes Details →
13.6.0 10 Aug 2018 M2 BSD-3-Clause Yes Details →
13.5.2 30 Jul 2018 M2 BSD-3-Clause Yes Details →
13.5.1 30 Jul 2018 M2 BSD-3-Clause Yes Details →
13.5.0 30 Jul 2018 M2 BSD-3-Clause Yes Details →
13.4.0 06 Jun 2018 M2 BSD-3-Clause Yes Details →
13.3.0 08 May 2018 M2 BSD-3-Clause Yes Details →
13.2.0 17 Apr 2018 M2 BSD-3-Clause Yes Details →
13.1.2 02 Feb 2018 M2 BSD-3-Clause Yes Details →
13.1.1 19 Jan 2018 M2 BSD-3-Clause Yes Details →
13.1.0 04 Jan 2018 M2 BSD-3-Clause Yes Details →
13.0.2 12 Nov 2017 M2 BSD-3-Clause Yes Details →
13.0.1 19 Oct 2017 M2 BSD-3-Clause Yes Details →
13.0.0 14 Oct 2017 M2 BSD-3-Clause Yes Details →
12.0.0 14 Oct 2017 M2 BSD-3-Clause Yes Details →
11.4.0 14 Oct 2017 M2 BSD-3-Clause Yes Details →
11.3.4 09 Oct 2017 M2 BSD-3-Clause Yes Details →
11.3.3 09 Oct 2017 M2 BSD-3-Clause Yes Details →
11.3.2 08 Oct 2017 M2 BSD-3-Clause Yes Details →
11.3.0 08 Oct 2017 M2 BSD-3-Clause Yes Details →
11.2.0 07 Oct 2017 M2 BSD-3-Clause Yes Details →
11.1.1 25 Sep 2017 M2 BSD-3-Clause Yes Details →
11.1.0 24 Sep 2017 M2 BSD-3-Clause Yes Details →
11.0.3 20 Sep 2017 M2 BSD-3-Clause Yes Details →
11.0.2 19 Sep 2017 M2 BSD-3-Clause Yes Details →
11.0.1 14 Sep 2017 M2 BSD-3-Clause Yes Details →
11.0.0 14 Sep 2017 M2 BSD-3-Clause Yes Details →
10.6.0 15 Jun 2017 M2 BSD-3-Clause Yes Details →
10.5.2 30 May 2017 M2 — Yes Details →
10.5.1 28 May 2017 M2 — Yes Details →
10.5.0 18 May 2017 M2 — Yes Details →
10.4.2 13 May 2017 M2 — Yes Details →
10.4.1 02 Apr 2017 M2 — Yes Details →
10.4.0 02 Apr 2017 M2 — Yes Details →
10.3.4 01 Apr 2017 M2 — Yes Details →
10.3.3 31 Mar 2017 M2 — Yes Details →
10.3.2 31 Mar 2017 M2 — Yes Details →
10.3.1 26 Mar 2017 M2 — Yes Details →
10.3.0 22 Mar 2017 M2 — Yes Details →
10.2.2 09 Feb 2017 M2 — Yes Details →
10.2.1 02 Feb 2017 M2 — Yes Details →
10.2.0 15 Jan 2017 M2 — Yes Details →
10.1.0 23 Dec 2016 M2 — Yes Details →
10.0.6 14 Dec 2016 M2 — Yes Details →
10.0.5 05 Dec 2016 M2 — Yes Details →
10.0.4 05 Dec 2016 M2 — Yes Details →
10.0.2 01 Dec 2016 M2 — Yes Details →
10.0.1 18 Nov 2016 M2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 8

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

03 Vulnerabilities

Recorded vulnerabilities for joi

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2026-92599: Joi Package Vulnerability Due to Quadratic Regular-Expression Backtracking 7.5 high 17.13.7 29 Sep 2026
High Severity Regular Expression Denial of Service in Joi Package 7.5 high No fix published 17 Sep 2026
CVE-2026-48038: joi Package Experiences Uncaught RangeError on Deeply Nested Input 5.3 medium 18.2.1 11 Jun 2026
CVE-2026-84368: joi Package Prototype Pollution via Custom Messages 3.7 low 17.13.6 08 Sep 2026
CVE-2026-84368: joi Package Prototype Pollution via Custom Messages 3.7 low 17.13.6 08 Sep 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: 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 joi

Is joi safe to use?

Vulert records 8 vulnerabilities for joi in npm: 0 critical, 2 high, 2 medium and 4 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is joi's Vulert package health score?

Vulert scores joi 60/100, which reads as usable, but worth attention. 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 current release has a vulnerability with no published fix, which caps this score.

Is the latest version of joi affected?

Yes. 18.3.0, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does joi have?

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

How often are new joi vulnerabilities disclosed?

8 vulnerabilities were recorded for joi in the last 12 months, and the oldest entry in this database dates to 11 Jun 2026. 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 joi 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 joi for upcoming vulnerabilities?

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