Quick answers
- Is CVE-2026-7009 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-7009 being exploited in the wild.
- How severe is CVE-2026-7009?
- Medium severity, with a CVSS score of 5.3, published 13 May 2026.
- Which products and versions are affected?
- curl curl 8.17.0 to 8.19.0; curl libcurl 8.17.0 to 8.19.0.
- Is there a fix for CVE-2026-7009?
- A patch was published on 2026-04-29: Fixed in curl version 8.20.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-7009 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-7009?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability classified as Improper Certificate Validation (CWE-295) exists in curl when using the Certificate Status Request TLS extension (OCSP stapling). The flaw occurs specifically when curl is built with an OpenSSL-based backend (including BoringSSL, AWS-LC, LibreSSL, or QuicTLS) and utilizes Apple SecTrust to access the native CA store on Apple operating systems. In this configuration, curl fails to detect OCSP problems, wrongly considering invalid or problematic responses as valid. This allows a remote server to bypass certificate status checks. The issue was introduced in version 8.17.0 and is fixed in version 8.20.0.
Affected products
- curl curl 8.17.0 to 8.19.0
- curl libcurl 8.17.0 to 8.19.0
Timeline
- 2026-04-25: other: Reported to the curl project
- 2026-04-29: patched: Fixed in curl version 8.20.0
- 2026-04-29: advisory: Project advisory published
- 2026-05-13: disclosed: NVD publication date