Publisher not identified
Python
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2020-10735 | 9 Sep 2022 | python 3.7 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2021-4189 | 24 Aug 2022 | Fixed in python 3.6.14, python 3.7.11, python 3.8.9, python 3.9.3, python 3.10.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2021-3733 | 7 Mar 2022 | Fixed in python v3.6.14, python v3.7.11, python v3.8.10, python v3.9.5. | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2021-3737 | 4 Mar 2022 | Fixed in python v3.6.14, python v3.7.11, python v3.8.11, python v3.9.6, python v3.10.0b2 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2022-0391 | 9 Feb 2022 | python 3.10.0b1, python 3.9.5, python 3.8.11, python 3.7.11, python 3.6.14 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2021-3426 | 20 May 2021 | python 3.8.9, python 3.9.3, python 3.10.0a7 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2019-5010 | 31 Oct 2019 | Python.org CPython 2.7.11 Python.org CPython 3.6.6 Python.org CPython 3.5.2 Python.org CPython 3 master at 480833808e918a1dcebbbcfd07d5a8de3c5c2a66 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.