VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

validator: vulnerability history, versions and safety

validator is a package in the npm ecosystem. Vulert records 11 vulnerabilities for it across 120 releases, from Oct 2017 to Nov 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded H2 M9
i
1 with no fix published

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

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

Most recent disclosure 27 Nov 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all validator vulnerabilities

Vulert verdict on validator 13.15.35 i

Updated on 22 Oct 2026

Careful: 13.15.35 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 Minor 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 13.15.35 — affected i
  • Vulnerabilities on record 11 over 8 years · 1 in the last year i
  • Latest disclosure 27 Nov 2025 i
  • Highest CVSS 7.5 i
  • With no published fix 1 i
  • Depended on by 39,254 packages i
  • Stars 23,737 i
  • OpenSSF scorecard 5/10 i
  • Last release 6 months ago i
  • Licence MIT 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 validator, 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
13.15.35 02 Apr 2026 M1 MIT No Details →
13.15.26 18 Dec 2025 M1 MIT No Details →
13.15.23 10 Nov 2025 M1 MIT No Details →
13.15.22 09 Nov 2025 M1 MIT No Details →
13.15.20 26 Oct 2025 H1 M1 MIT No Details →
13.15.15 28 May 2025 H1 M1 MIT No Details →
13.15.0 24 Mar 2025 H1 M1 MIT No Details →
13.12.0 09 May 2024 H1 M1 MIT No Details →
13.11.0 04 Aug 2023 H1 M1 MIT No Details →
13.9.0 02 Feb 2023 H1 M1 MIT No Details →
13.7.0 01 Nov 2021 H1 M1 MIT No Details →
13.6.0 20 Apr 2021 H1 M3 MIT No Details →
13.5.2 10 Dec 2020 H1 M3 MIT No Details →
13.5.1 30 Nov 2020 H1 M3 MIT No Details →
13.5.0 30 Nov 2020 H1 M3 MIT No Details →
13.1.17 18 Sep 2020 H1 M3 MIT No Details →
13.1.1 11 Jun 2020 H1 M3 MIT No Details →
13.1.0 10 Jun 2020 H1 M3 MIT No Details →
13.0.0 20 Mar 2020 H1 M3 MIT No Details →
12.2.0 25 Jan 2020 H1 M3 MIT No Details →
12.1.0 21 Nov 2019 H1 M3 MIT No Details →
12.0.0 27 Oct 2019 H1 M3 MIT No Details →
11.1.0 04 Jul 2019 H1 M3 MIT No Details →
11.0.0 23 May 2019 H1 M2 MIT No Details →
10.11.0 15 Jan 2019 H1 M2 MIT No Details →
10.10.0 23 Dec 2018 H1 M2 MIT No Details →
10.9.0 07 Nov 2018 H1 M2 MIT No Details →
10.8.0 24 Sep 2018 H1 M2 MIT No Details →
10.7.1 02 Sep 2018 H1 M2 MIT No Details →
10.7.0 24 Aug 2018 H1 M2 MIT No Details →
10.6.0 17 Aug 2018 H1 M2 MIT No Details →
10.5.0 03 Aug 2018 H1 M2 MIT No Details →
10.4.0 19 Jun 2018 H1 M2 MIT No Details →
10.3.0 03 Jun 2018 H1 M2 MIT No Details →
10.2.0 10 May 2018 H1 M2 MIT No Details →
10.1.0 04 May 2018 H1 M2 MIT No Details →
10.0.0 03 May 2018 H1 M2 MIT No Details →
9.4.1 18 Feb 2018 H1 M2 MIT No Details →
9.4.0 30 Jan 2018 H1 M2 MIT No Details →
9.3.0 26 Jan 2018 H1 M2 MIT No Details →
9.2.0 09 Dec 2017 H1 M2 MIT No Details →
9.1.2 24 Nov 2017 H1 M2 MIT No Details →
9.1.1 25 Oct 2017 H1 M2 MIT No Details →
9.1.0 24 Oct 2017 H1 M2 MIT No Details →
9.0.0 29 Sep 2017 H1 M2 MIT No Details →
8.2.0 09 Sep 2017 H1 M2 MIT No Details →
8.1.0 22 Aug 2017 H1 M2 MIT No Details →
8.0.0 07 Jul 2017 H1 M2 MIT No Details →
7.2.0 29 Jun 2017 H1 M2 MIT No Details →
7.1.0 22 Jun 2017 H1 M2 MIT No Details →
7.0.0 25 Feb 2017 H1 M2 MIT No Details →
6.3.0 24 Feb 2017 H1 M2 MIT No Details →
6.2.1 06 Jan 2017 H1 M2 MIT No Details →
6.2.0 28 Nov 2016 H1 M2 MIT No Details →
6.1.0 15 Oct 2016 H1 M2 MIT No Details →
6.0.0 27 Sep 2016 H1 M2 MIT No Details →
5.7.0 11 Sep 2016 H1 M2 MIT No Details →
5.6.0 01 Sep 2016 H1 M2 MIT No Details →
5.5.0 21 Jul 2016 H1 M2 MIT No Details →
5.4.0 09 Jun 2016 H1 M2 MIT No Details →
5.3.0 28 May 2016 H1 M2 MIT No Details →
5.2.0 04 Apr 2016 H1 M2 MIT No Details →
5.1.0 29 Feb 2016 H1 M2 MIT No Details →
5.0.0 21 Feb 2016 H1 M2 MIT No Details →
4.9.0 18 Feb 2016 H1 M2 MIT No Details →
4.8.0 10 Feb 2016 H1 M2 MIT No Details →
4.7.1 05 Feb 2016 H1 M2 MIT No Details →
4.7.0 04 Feb 2016 H1 M2 MIT No Details →
4.6.1 03 Feb 2016 H1 M2 MIT No Details →
4.6.0 03 Feb 2016 H1 M2 MIT No Details →
4.5.2 28 Jan 2016 H1 M2 MIT No Details →
4.5.1 20 Jan 2016 H1 M2 MIT No Details →
4.5.0 05 Jan 2016 H1 M2 MIT No Details →
4.4.0 04 Dec 2015 H1 M2 MIT No Details →
4.3.0 20 Nov 2015 H1 M2 MIT No Details →
4.2.1 27 Oct 2015 H1 M2 MIT No Details →
4.2.0 20 Oct 2015 H1 M2 MIT No Details →
4.1.0 05 Oct 2015 H1 M2 MIT No Details →
4.0.6 18 Sep 2015 H1 M2 MIT No Details →
4.0.5 17 Aug 2015 H1 M2 MIT No Details →
4.0.4 17 Aug 2015 H1 M2 MIT No Details →
4.0.3 15 Aug 2015 H1 M2 MIT No Details →
4.0.2 04 Aug 2015 H1 M2 MIT No Details →
4.0.1 03 Aug 2015 H1 M2 MIT No Details →
4.0.0 31 Jul 2015 H1 M2 MIT No Details →
3.43.0 29 Jul 2015 H1 M2 MIT No Details →
3.42.0 28 Jul 2015 H1 M2 MIT No Details →
3.41.3 27 Jul 2015 H1 M2 MIT No Details →
3.41.2 08 Jul 2015 H1 M2 MIT No Details →
3.41.1 06 Jul 2015 H1 M2 MIT No Details →
3.41.0 06 Jul 2015 H1 M2 MIT No Details →
3.40.1 11 Jun 2015 H1 M2 MIT No Details →
3.40.0 20 May 2015 H1 M2 MIT No Details →
3.39.0 22 Apr 2015 H1 M2 MIT No Details →
3.38.0 16 Apr 2015 H1 M2 MIT No Details →
3.37.0 01 Apr 2015 H1 M2 MIT No Details →
3.36.0 30 Mar 2015 H1 M2 MIT No Details →
3.35.0 23 Mar 2015 H1 M2 MIT No Details →
3.34.0 15 Mar 2015 H1 M2 MIT No Details →
3.33.0 03 Mar 2015 H1 M2 MIT No Details →
3.32.0 23 Feb 2015 H1 M2 — No Details →
3.30.0 12 Feb 2015 H1 M2 — No Details →
3.29.0 10 Feb 2015 H1 M2 — No Details →
3.28.0 24 Jan 2015 H1 M2 — No Details →
3.27.0 29 Dec 2014 H1 M2 — No Details →
3.26.0 18 Dec 2014 H1 M2 — No Details →
3.25.0 17 Dec 2014 H1 M2 — No Details →
3.24.0 12 Dec 2014 H1 M2 — No Details →
3.23.0 11 Dec 2014 H1 M2 — No Details →
3.22.2 05 Dec 2014 H1 M2 — No Details →
3.22.1 29 Oct 2014 H1 M2 — No Details →
3.22.0 18 Oct 2014 H2 M2 — No Details →
3.21.0 16 Oct 2014 H2 M2 — No Details →
3.20.0 14 Oct 2014 H2 M2 — No Details →
3.19.1 05 Oct 2014 H2 M2 — No Details →
3.19.0 21 Sep 2014 H2 M2 — No Details →
3.18.1 14 Sep 2014 H2 M2 — No Details →
3.18.0 09 Sep 2014 H2 M2 — No Details →
3.17.2 09 Sep 2014 H2 M2 — No Details →
3.17.1 28 Aug 2014 H2 M2 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 5
  • 2018 1
  • 2020 1
  • 2021 2
  • 2025 2

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

03 Vulnerabilities

Recorded vulnerabilities for validator

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2014-8882: Regular Expression Denial of Service in validator 7.5 high 3.22.1 31 Aug 2020
CVE-2025-12758: Validator Package Vulnerable to Incomplete Filtering of Special Elements 7.5 high 13.15.22 27 Nov 2025
CVE-2013-7453: XSS Bypass in validator 6.1 medium 1.1.0 24 Oct 2017
CVE-2014-9772: XSS Filter Bypass in validator 6.1 medium 2.0.0 06 Nov 2018
CVE-2013-7454: XSS Filter Bypasses in validator 6.1 medium 1.1.0 24 Oct 2017

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 validator

Is validator safe to use?

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

What is validator's Vulert package health score?

Vulert scores validator 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 validator affected?

Yes. 13.15.35, 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.

Which version of validator should I use?

13.15.35 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 validator have?

11 vulnerabilities are recorded for validator in the npm ecosystem: 0 critical, 2 high, 9 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 validator vulnerabilities disclosed?

1 vulnerability was recorded for validator in the last 12 months, and the oldest entry in this database dates to 24 Oct 2017. 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 validator 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 validator for upcoming vulnerabilities?

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