VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

validators: vulnerability history, versions and safety

validators is a package in the PyPI ecosystem. Vulert records 3 vulnerabilities for it across 4 releases, from Dec 2019 to Jan 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H1 U2
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 validators vulnerabilities

Vulert verdict on validators 0.36.0 i

Updated on 23 Oct 2026

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

Package health score 88/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 0.36.0 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 21 Jan 2020 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 2,306 packages i
  • Stars 1,131 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, 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 validators, 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.36.0 11 Oct 2026 none MIT — Details →
0.35.0 01 May 2025 none MIT — Details →
0.34.0 03 Sep 2024 none MIT — Details →
0.33.0 15 Jul 2024 none MIT — Details →
0.32.0 10 Jul 2024 none MIT — Details →
0.31.0 08 Jul 2024 none MIT — Details →
0.30.0 04 Jul 2024 none MIT — Details →
0.29.0 01 Jul 2024 none MIT — Details →
0.28.3 25 May 2024 none MIT — Details →
0.28.2 24 May 2024 none MIT — Details →
0.28.1 19 Apr 2024 none MIT — Details →
0.28.0 04 Apr 2024 none MIT — Details →
0.27.0 03 Apr 2024 none MIT — Details →
0.26.0 02 Apr 2024 none MIT — Details →
0.25.0 02 Apr 2024 none MIT — Details →
0.24.0 24 Mar 2024 none MIT — Details →
0.23.2 20 Mar 2024 none MIT — Details →
0.23.1 19 Mar 2024 none MIT — Details →
0.23.0 19 Mar 2024 none MIT — Details →
0.22.0 02 Sep 2023 none MIT — Details →
0.21.2 11 Aug 2023 none MIT — Details →
0.21.1 11 Aug 2023 none MIT — Details →
0.21.0 11 Aug 2023 none MIT — Details →
0.20.0 05 Jun 2022 none MIT — Details →
0.19.0 04 May 2022 none MIT — Details →
0.18.2 18 Dec 2020 none MIT — Details →
0.18.1 03 Sep 2020 none MIT — Details →
0.18.0 19 Aug 2020 none MIT — Details →
0.17.1 03 Aug 2020 none MIT — Details →
0.17.0 02 Aug 2020 none MIT — Details →
0.16.0 16 Jul 2020 none MIT — Details →
0.15.0 07 May 2020 none MIT — Details →
0.14.3 02 Apr 2020 none MIT — Details →
0.14.2 24 Jan 2020 none MIT — Details →
0.14.1 04 Dec 2019 none MIT — Details →
0.14.0 21 Aug 2019 none non-standard — Details →
0.13.0 20 May 2019 none non-standard — Details →
0.12.6 08 May 2019 none non-standard — Details →
0.12.5 15 Apr 2019 H1 U2 non-standard Yes Details →
0.12.4 02 Jan 2019 H1 U2 non-standard Yes Details →
0.12.3 13 Nov 2018 H1 U2 non-standard Yes Details →
0.12.2 03 Jun 2018 H1 U2 non-standard Yes Details →
0.12.1 30 Jan 2018 none non-standard — Details →
0.12.0 03 Jun 2017 none non-standard — Details →
0.11.3 27 Mar 2017 none non-standard — Details →
0.11.2 08 Jan 2017 none non-standard — Details →
0.11.1 19 Nov 2016 none non-standard — Details →
0.11.0 30 Aug 2016 none non-standard — Details →
0.10.3 13 Jun 2016 none non-standard — Details →
0.10.2 11 Jun 2016 none non-standard — Details →
0.10.1 09 May 2016 none non-standard — Details →
0.10.0 09 Jan 2016 none non-standard — Details →
0.9.0 10 Oct 2015 none non-standard — Details →
0.8.0 24 Jun 2015 none non-standard — Details →
0.7.0 07 Sep 2014 none non-standard — Details →
0.6.0 25 Jun 2014 none non-standard — Details →
0.5.0 31 Oct 2013 none non-standard — Details →
0.4.0 29 Oct 2013 none non-standard — Details →
0.3.0 27 Oct 2013 none non-standard — Details →
0.2.0 22 Oct 2013 none non-standard — Details →
0.1.0 17 Oct 2013 none non-standard — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 2
  • 2020 1

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

03 Vulnerabilities

Recorded vulnerabilities for validators

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2019-19588: Uncontrolled resource consumption in validators Python package 7.5 high 0.12.6 21 Jan 2020
CVE-2019-19588: Infinite Loop Vulnerability in validators Package N/A unrated 0.12.6 05 Dec 2019
CVE-2019-19588: Infinite Loop Vulnerability in validators Package N/A unrated 0.12.6 05 Dec 2019

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 validators

Is validators safe to use?

Vulert records 3 vulnerabilities for validators in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is validators's Vulert package health score?

Vulert scores validators 88/100, which reads as healthy. 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 validators affected?

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

Which version of validators should I use?

0.36.0 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 validators have?

3 vulnerabilities are recorded for validators in the PyPI ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new validators vulnerabilities disclosed?

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

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