curl vulnerabilities and fixes
Recent CVEs affecting curl, with upgrade or downgrade steps. 7 tracked.
curl has 7 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 7. Most recent: 2023-05-26. Highest priority: CVE-2023-27534 (score 57/100).
- CVE-2023-27534 HIGH 8.8 UPGRADE MITIGATE A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde (~) character to be
- CVE-2023-28319 HIGH 7.5 UPGRADE UPGRADE A use after free vulnerability exists in curl <v8.1.0 in the way libcurl offers a feature to verify an SSH ser
- CVE-2023-28321 MEDIUM 5.9 UPGRADE MITIGATE An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of wil
- CVE-2022-43552 MEDIUM 5.9 UPGRADE UPGRADE A use after free vulnerability exists in curl <7.87.0
- CVE-2023-23916 MEDIUM 6.5 UPGRADE MITIGATE An allocation of resources without limits or throttling vulnerability exists in curl <v7.88.0 based on the "ch
- CVE-2023-28320 MEDIUM 5.9 UPGRADE UPGRADE A denial of service vulnerability exists in curl <v8.1.0 in the way libcurl provides several different backend
- CVE-2023-28322 LOW 3.7 UPGRADE MITIGATE An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might err
FAQ
How do I fix curl vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is curl being exploited right now?
None of the tracked curl CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which curl CVE should I patch first?
CVE-2023-27534 currently ranks highest (57/100): A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde (~) character to be .