Vulnerability Database · npm · Package report

nocodb: vulnerability history, versions and safety

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

i
54 vulnerabilities recorded H7 M40 L7
i
13 with no fix published

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

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

Most recent disclosure 17 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on nocodb 0.301.3 i

Updated on 22 Oct 2026

Careful: 0.301.3 has 29 known vulnerabilities, and 13 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Niche
  • 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 0.301.3 — affected i
  • Vulnerabilities on record 54 over 4 years · 43 in the last year i
  • Latest disclosure 17 Jun 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 13 i
  • Stars 65,290 i
  • OpenSSF scorecard 4/10 i
  • Last release 7 months ago i
  • Licence non-standard 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 nocodb, 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.301.3 27 Feb 2026 H2 M22 L5 non-standard No Details →
0.301.2 21 Jan 2026 H2 M30 L7 non-standard No Details →
0.301.1 14 Jan 2026 H2 M30 L7 non-standard No Details →
0.301.0 13 Jan 2026 H2 M30 L7 AGPL-3.0-or-later No Details →
0.300.0 13 Jan 2026 H3 M33 L7 AGPL-3.0-or-later No Details →
0.265.1 03 Oct 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.265.0 01 Oct 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.264.9 22 Sep 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.264.8 18 Sep 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.264.7 16 Sep 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.264.6 18 Aug 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.264.4 06 Aug 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.264.3 04 Aug 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.264.2 31 Jul 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.264.1 30 Jul 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.264.0 28 Jul 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.263.8 16 Jun 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.263.7 14 Jun 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.263.6 13 Jun 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.263.4 19 May 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.263.3 16 May 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.263.2 16 May 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.263.1 05 May 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.263.0 30 Apr 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.262.5 24 Mar 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.262.4 22 Mar 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.262.3 20 Mar 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.262.2 10 Mar 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.262.1 26 Feb 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.262.0 20 Feb 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.261.0 18 Feb 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.260.7 12 Feb 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.260.6 08 Feb 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.260.5 06 Feb 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.260.4 04 Feb 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.260.3 04 Feb 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.260.2 14 Jan 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.260.1 09 Jan 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.260.0 04 Jan 2025 H3 M33 L7 AGPL-3.0-or-later No Details →
0.258.11 30 Dec 2024 H3 M33 L7 AGPL-3.0-or-later No Details →
0.258.10 20 Dec 2024 H3 M33 L7 AGPL-3.0-or-later No Details →
0.258.7 12 Dec 2024 H3 M33 L7 AGPL-3.0-or-later No Details →
0.258.3 28 Nov 2024 H3 M33 L7 AGPL-3.0-or-later No Details →
0.258.2 19 Nov 2024 H3 M33 L7 AGPL-3.0-or-later No Details →
0.258.1 19 Nov 2024 H3 M33 L7 AGPL-3.0-or-later No Details →
0.258.0 12 Nov 2024 H3 M33 L7 AGPL-3.0-or-later No Details →
0.257.2 16 Oct 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.257.0 09 Oct 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.256.0 09 Oct 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.255.2 29 Aug 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.255.1 29 Aug 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.255.0 15 Aug 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.254.1 14 Aug 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.252.0 08 Aug 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.251.3 26 Jul 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.251.2 23 Jul 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.251.1 03 Jul 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.251.0 25 Jun 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.250.2 14 Jun 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.250.1 13 Jun 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.250.0 13 Jun 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.207.3 29 May 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.207.2 18 May 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.207.1 15 May 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.207.0 06 May 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.205.1 04 Apr 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.205.0 02 Apr 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.204.9 23 Mar 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.204.8 22 Mar 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.204.7 19 Mar 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.204.6 19 Mar 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.204.5 14 Mar 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.204.4 04 Mar 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.204.3 01 Mar 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.204.2 01 Mar 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.204.1 23 Feb 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.204.0 11 Jan 2024 H3 M34 L7 AGPL-3.0-or-later No Details →
0.203.2 29 Dec 2023 H3 M34 L7 AGPL-3.0-or-later No Details →
0.203.1 29 Dec 2023 H3 M34 L7 AGPL-3.0-or-later No Details →
0.203.0 28 Dec 2023 H3 M34 L7 AGPL-3.0-or-later No Details →
0.202.10 13 Dec 2023 H3 M34 L7 AGPL-3.0-or-later No Details →
0.202.9 30 Nov 2023 H3 M36 L7 AGPL-3.0-or-later No Details →
0.202.8 20 Nov 2023 H4 M36 L7 AGPL-3.0-or-later No Details →
0.202.7 16 Nov 2023 H4 M36 L7 AGPL-3.0-or-later No Details →
0.202.6 16 Nov 2023 H4 M36 L7 AGPL-3.0-or-later No Details →
0.202.5 20 Oct 2023 H4 M35 L7 AGPL-3.0-or-later No Details →
0.202.4 11 Oct 2023 H4 M35 L7 AGPL-3.0-or-later No Details →
0.202.0 11 Oct 2023 H4 M35 L7 AGPL-3.0-or-later No Details →
0.200.0 11 Oct 2023 H4 M35 L7 AGPL-3.0-or-later No Details →
0.111.4 11 Sep 2023 H4 M35 L7 AGPL-3.0-or-later No Details →
0.111.3 08 Sep 2023 H4 M35 L7 AGPL-3.0-or-later No Details →
0.111.2 07 Sep 2023 H4 M35 L7 AGPL-3.0-or-later No Details →
0.111.1 01 Sep 2023 H4 M35 L7 AGPL-3.0-or-later No Details →
0.111.0 25 Aug 2023 H4 M35 L7 AGPL-3.0-or-later No Details →
0.109.7 14 Aug 2023 H4 M36 L7 AGPL-3.0-or-later No Details →
0.109.6 02 Aug 2023 H4 M36 L7 AGPL-3.0-or-later No Details →
0.109.5 28 Jul 2023 H4 M36 L7 AGPL-3.0-or-later No Details →
0.109.4 11 Jul 2023 H4 M36 L7 AGPL-3.0-or-later No Details →
0.109.3 28 Jun 2023 H4 M36 L7 AGPL-3.0-or-later No Details →
0.109.2 21 Jun 2023 H4 M36 L7 AGPL-3.0-or-later No Details →
0.109.1 14 Jun 2023 H4 M36 L7 — No Details →
0.109.0 13 Jun 2023 H4 M36 L7 — No Details →
0.108.1 31 May 2023 H4 M36 L7 — No Details →
0.108.0 31 May 2023 H4 M36 L7 — No Details →
0.108.0-beta.0 29 May 2023 H4 M36 L7 — No Details →
0.107.5 27 May 2023 H4 M36 L7 — No Details →
0.107.4 24 May 2023 H4 M36 L7 — No Details →
0.107.3 22 May 2023 H4 M36 L7 — No Details →
0.107.2 22 May 2023 H4 M36 L7 — No Details →
0.107.1 20 May 2023 H4 M36 L7 — No Details →
0.107.0 19 May 2023 H4 M36 L7 — No Details →
0.107.0-beta.1 11 May 2023 H4 M36 L7 — No Details →
0.107.0-beta.0 04 May 2023 H4 M36 L7 — No Details →
0.106.1 18 Apr 2023 H4 M36 L7 — No Details →
0.106.0 11 Apr 2023 H4 M36 L7 — No Details →
0.106.0-beta.1 06 Apr 2023 H4 M36 L7 — No Details →
0.106.0-beta.0 31 Mar 2023 H4 M36 L7 — No Details →
0.105.3 21 Feb 2023 H4 M36 L7 — No Details →
0.105.2 17 Feb 2023 H4 M36 L7 — No Details →
0.105.1 17 Feb 2023 H4 M36 L7 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 5
  • 2023 2
  • 2024 3
  • 2025 1
  • 2026 43

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

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 nocodb

Is nocodb safe to use?

Vulert records 54 vulnerabilities for nocodb in npm: 0 critical, 7 high, 40 medium and 7 low. 13 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is nocodb's Vulert package health score?

Vulert scores nocodb 50/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 nocodb affected?

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

Which version of nocodb should I use?

0.301.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 nocodb have?

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

How often are new nocodb vulnerabilities disclosed?

43 vulnerabilities were recorded for nocodb in the last 12 months, and the oldest entry in this database dates to 14 Jun 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 nocodb 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 nocodb for upcoming vulnerabilities?

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