← Search results
CVE-LINKED INVENTORY50 SECURITY RECORDS
Publisher not identified
https://github.com/curl/curl
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-2023-28322 | 26 May 2023 | Fixed in 8.1.0 | Update to V2.17.0 or later version | Update reference ↗ |
| CVE-2023-28321 | 26 May 2023 | Fixed in 8.1.0 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2023-28320 | 26 May 2023 | Fixed in 8.1.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-28319 | 26 May 2023 | Fixed in 8.1.0 | Update to V2.4.8 or later version | Update reference ↗ |
| CVE-2023-27538 | 30 Mar 2023 | Fixed in 8.0.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2023-27537 | 30 Mar 2023 | Fixed in 8.0.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2023-27536 | 30 Mar 2023 | Fixed in 8.0.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2023-27535 | 30 Mar 2023 | Fixed in 8.0.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2023-27533 | 30 Mar 2023 | Fixed in 8.0.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2023-23916 | 23 Feb 2023 | Fixed in 7.88.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2023-23915 | 23 Feb 2023 | Fixed in 7.88.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2023-23914 | 23 Feb 2023 | Fixed in 7.88.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2022-43552 | 9 Feb 2023 | Fixed in curl 7.87.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2022-43551 | 23 Dec 2022 | Fixed in curl 7.87.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2022-35260 | 5 Dec 2022 | Fixed in 7.86.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2022-32221 | 5 Dec 2022 | Fixed in 7.86.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2022-35252 | 23 Sep 2022 | Fixed in curl 7.85.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2022-32208 | 7 Jul 2022 | Fixed in 7.84.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2022-32207 | 7 Jul 2022 | Fixed in 7.84.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2022-32206 | 7 Jul 2022 | Fixed in 7.84.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2022-32205 | 7 Jul 2022 | Fixed in 7.84.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2022-27778 | 1 Jun 2022 | fixed in 7.83.1 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2022-30115 | 1 Jun 2022 | Fixed in 7.83.1 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2022-27782 | 1 Jun 2022 | Fixed in 7.83.1 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2022-27781 | 1 Jun 2022 | Fixed in 7.83.1 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2022-27780 | 1 Jun 2022 | Fixed in 7.83.1 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2022-27779 | 1 Jun 2022 | Fixed in 7.83.1 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2022-27776 | 1 Jun 2022 | fixed in curl 7.83.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2022-27775 | 1 Jun 2022 | curl 7.65.0 to 7.82.0 are vulnerable | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2022-27774 | 1 Jun 2022 | curl 4.9 to and include curl 7.82.0 are affected | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2022-22576 | 26 May 2022 | Fixed in curl 7.83.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2021-22947 | 29 Sep 2021 | curl 7.20.0 to and including 7.78.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2021-22946 | 29 Sep 2021 | curl 7.20.0 to and including 7.78.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2021-22945 | 23 Sep 2021 | curl 7.73.0 to and including 7.78.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2021-22924 | 5 Aug 2021 | curl 7.10.4 to and include curl 7.77.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2021-22926 | 5 Aug 2021 | curll 7.33.0 to and include 7.77.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2021-22925 | 5 Aug 2021 | curl 7.7 to and including 7.77.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2021-22923 | 5 Aug 2021 | curl 7.27.0 to and including 7.77.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2021-22922 | 5 Aug 2021 | curl 7.27.0 to and including 7.77.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2021-22901 | 11 Jun 2021 | 7.75.0 through 7.76.1 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2021-22897 | 11 Jun 2021 | 7.61.0 through 7.76.1 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2021-22898 | 11 Jun 2021 | 7.7 through 7.76.1 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2021-22890 | 1 Apr 2021 | 7.63.0 to and including 7.75.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2021-22876 | 1 Apr 2021 | 7.1.1 to and including 7.75.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2020-8177 | 14 Dec 2020 | curl 7.20.0 to and including 7.70.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2020-8169 | 14 Dec 2020 | libcurl 7.62.0 to and including 7.70.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2020-8286 | 14 Dec 2020 | 7.41.0 to and including 7.73.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2020-8231 | 14 Dec 2020 | libcurl 7.29.0 to and including 7.71.1 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2020-8285 | 14 Dec 2020 | libcurl 7.21.0 to and including 7.73.0 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2020-8284 | 14 Dec 2020 | 7.73.0 and earlier | Update to V3.1.5 or later version | Update reference ↗ |
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.