VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

datatables.net: vulnerability history, versions and safety

datatables.net is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 19 releases, from Dec 2020 to Sep 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 H1 M1
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 datatables.net vulnerabilities

Vulert verdict on datatables.net 3.1.4 i

Updated on 23 Oct 2026

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

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

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

  • Current release 3.1.4 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 29 Sep 2021 i
  • Highest CVSS 7.3 i
  • With no published fix 0 i
  • Depended on by 355 packages i
  • Stars 806 i
  • OpenSSF scorecard 2/10 i
  • Last release this month 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 datatables.net, 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
3.1.4 13 Oct 2026 none MIT — Details →
3.1.3 02 Oct 2026 none MIT — Details →
3.1.2 25 Sep 2026 none MIT — Details →
3.1.1 22 Sep 2026 none MIT — Details →
3.1.0 22 Sep 2026 none MIT — Details →
3.0.4 11 Sep 2026 none MIT — Details →
3.0.3 31 Aug 2026 none MIT — Details →
3.0.2 18 Aug 2026 none MIT — Details →
3.0.1 31 Jul 2026 none MIT — Details →
3.0.0 24 Jul 2026 none MIT — Details →
3.0.0-beta.2 27 Apr 2026 none MIT — Details →
2.3.8 27 Apr 2026 none MIT — Details →
3.0.0-beta.1 07 Apr 2026 none MIT — Details →
2.3.7 30 Jan 2026 none MIT — Details →
2.3.6 23 Dec 2025 none MIT — Details →
2.3.5 14 Nov 2025 none MIT — Details →
2.3.4 09 Sep 2025 none MIT — Details →
2.3.3 20 Aug 2025 none MIT — Details →
2.3.2 06 Jun 2025 none MIT — Details →
2.3.1 16 May 2025 none MIT — Details →
2.3.0 30 Apr 2025 none MIT — Details →
2.2.2 04 Feb 2025 none MIT — Details →
2.2.1 09 Jan 2025 none MIT — Details →
2.2.0 06 Jan 2025 none MIT — Details →
2.1.8 04 Oct 2024 none MIT — Details →
2.1.7 20 Sep 2024 none MIT — Details →
2.1.6 06 Sep 2024 none MIT — Details →
2.1.5 30 Aug 2024 none MIT — Details →
2.1.4 16 Aug 2024 none MIT — Details →
2.1.3 01 Aug 2024 none MIT — Details →
2.1.2 24 Jul 2024 none MIT — Details →
2.1.0 19 Jul 2024 none MIT — Details →
2.0.8 28 May 2024 none MIT — Details →
2.0.7 07 May 2024 none MIT — Details →
2.0.6 03 May 2024 none MIT — Details →
2.0.5 18 Apr 2024 none MIT — Details →
2.0.4 16 Apr 2024 none MIT — Details →
2.0.3 22 Mar 2024 none MIT — Details →
2.0.2 07 Mar 2024 none MIT — Details →
2.0.1 27 Feb 2024 none MIT — Details →
1.13.11 27 Feb 2024 none MIT — Details →
2.0.0 15 Feb 2024 none MIT — Details →
1.13.10 09 Feb 2024 none MIT — Details →
1.13.8 16 Nov 2023 none MIT — Details →
1.13.7 03 Nov 2023 none MIT — Details →
1.13.6 31 Jul 2023 none MIT — Details →
1.13.5 04 Jul 2023 none MIT — Details →
1.13.4 10 Mar 2023 none MIT — Details →
1.13.3 28 Feb 2023 none MIT — Details →
1.13.2 03 Feb 2023 none MIT — Details →
1.13.1 08 Nov 2022 none MIT — Details →
1.13.0 08 Nov 2022 none MIT — Details →
1.12.1 19 May 2022 none MIT — Details →
1.12.0 16 May 2022 none MIT — Details →
1.11.5 28 Feb 2022 none MIT — Details →
1.11.4 21 Jan 2022 none MIT — Details →
1.11.3 24 Sep 2021 none MIT — Details →
1.11.2 08 Sep 2021 M1 MIT Yes Details →
1.11.1 04 Sep 2021 M1 MIT Yes Details →
1.11.0 03 Sep 2021 M1 MIT Yes Details →
1.10.25 04 Jun 2021 M1 MIT Yes Details →
1.10.24 09 Mar 2021 M1 MIT Yes Details →
1.10.23 18 Dec 2020 M1 MIT Yes Details →
1.10.22 18 Sep 2020 M1 MIT Yes Details →
1.10.21 11 May 2020 H1 M1 MIT Yes Details →
1.10.20 01 Oct 2019 H1 M1 MIT Yes Details →
1.10.19 22 Jun 2018 H1 M1 MIT Yes Details →
1.10.18 19 Jun 2018 H1 M1 MIT Yes Details →
1.10.16 01 Sep 2017 H1 M1 MIT Yes Details →
1.10.15 18 Apr 2017 H1 M1 MIT Yes Details →
1.10.14 17 Apr 2017 H1 M1 MIT Yes Details →
2.1.1 18 Jan 2017 none MIT — Details →
1.10.13 06 Dec 2016 H1 M1 MIT Yes Details →
1.10.12 20 May 2016 H1 M1 MIT Yes Details →
1.10.11 11 Feb 2016 H1 M1 MIT Yes Details →
1.10.10 07 Nov 2015 H1 M1 MIT Yes Details →
1.10.9 07 Oct 2015 H1 M1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2021 1

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 datatables.net

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-28458: Prototype Pollution in datatables.net 7.3 high 1.10.22 17 Dec 2020
CVE-2021-23445: Cross-Site Scripting in datatables.net 6.1 medium 1.11.3 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: 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 datatables.net

Is datatables.net safe to use?

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

Vulert scores datatables.net 76/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 datatables.net affected?

No. 3.1.4, 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.

How many vulnerabilities does datatables.net have?

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

0 vulnerabilities were recorded for datatables.net in the last 12 months, and the oldest entry in this database dates to 17 Dec 2020. 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 datatables.net 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 datatables.net for upcoming vulnerabilities?

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