DataTables vulnerabilitiesDataTables: known vulnerabilities and safe versions
npm: datatables.net
DataTables has 6 known vulnerability records: 2 in the npm advisory data (GitHub Advisory Database via OSV, the same source npm audit uses) and 4 only in Retire.js (CDN builds and advisories without a CVE).
By branch: 1.x is safe from 1.11.3.
Vulnerabilities and safe version by branch
Safe version: on that branch, this release and every later one (up to the branch's latest release, where known) fall outside every known record's range. Candidates are only the records' own fixed versions and the branch's latest release; "No fix" means moving off the branch.
| Branch | Support | Latest on branch | Records | Safe version |
|---|---|---|---|---|
| 1.x | — | — | 6high | 1.11.3 |
Support dates appear only for libraries that endoflife.date tracks.
Records
Newest first. Ranges are the record's own data; several ranges mean separate fixes per branch.
medium 6.1
Fixed in: 1.11.3
EPSS 1.9%
CVE-2020-28458exploit code exists2020-12-16
All versions of package datatables.net are vulnerable to Prototype Pollution due to an incomplete fix for https://snyk.io/vuln/SNYK-JS-DATAT
Affected versions: < 1.10.22
high 7.3
Fixed in: 1.10.22
EPSS 3.7%
CVE-2015-65842015-09-11
Cross-site scripting (XSS) vulnerability in the DataTables plugin 1.10.8 and earlier for jQuery allows remote attackers to inject arbitrary
Affected versions: < 1.10.10
medium 4.3
Fixed in: 1.10.10
EPSS 2.6%
no CVE
possible XSS
Affected versions: < 1.11.3
low
Fixed in: 1.11.3
no CVE
prototype pollution
Affected versions: < 1.10.23
high
Fixed in: 1.10.23
no CVE
prototype pollution
Affected versions: < 1.10.22
medium
Fixed in: 1.10.22
Sources and method
Ranges: GitHub Advisory Database (OSV npm export, daily) and Retire.js (Apache-2.0). Exploitation: CISA KEV, FIRST EPSS and exploit maturity from the Noroxi CVE database. Support dates: endoflife.date.
This page and the JavaScript library scan use the same matching rule: a row without bounds is not evidence, and versions are compared in one place. A record without a version range never counts as "affected" in the version check.
Data as of October 21, 2026.