CVE-2019-19588 json
Uncontrolled resource consumption in validators Python package
published 2019-12-05 6 y ago modified 2026-06-17 4 mo ago also GHSA-5qcg-w2cc-xffw , PYSEC-2019-134 , EUVD-2019-0154
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
The validators package 0.12.2 through 0.12.5 for Python enters an infinite loop when validators.domain is called with a crafted domain string. This is fixed in 0.12.6.
Patch / fix
- pypi validators 0.12.6
- python-validators openSUSE Tumbleweed 0.35.0-1.4
- python-validators openSUSE Tumbleweed 0.24.0-1.2
opensuse advisories openSUSE-SU-2026:12046-1openSUSE-SU-2024:13811-1
Exploit prediction
1.47% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/kvesteri/validators/issues/86 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 7.8 | AV:N/AC:L/Au:N/C:N/I:N/A:C |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | validators | >=0.12.2, <0.12.6 |
0.12.6 |
Classification
- Weakness
-
- CWE-835 Loop with Unreachable Exit Condition
References
-
github.com
/kvesteri/validators/issues/86
web, exploit, third-party-advisory, report
-
nvd.nist.gov
/vuln/detail/CVE-2019-19588
advisory
-
github.com
/python-validators/validators/issues/86
web
-
github.com
/advisories/GHSA-5qcg-w2cc-xffw
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/validators/PYSEC-2019-134.yaml
web
-
github.com
/python-validators/validators
package
Sources
- CVE List CVE-2019-19588
- GitHub Advisory GHSA-5qcg-w2cc-xffw
- NVD CVE-2019-19588
- OSV PYSEC-2019-134
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.