No QUIC certificate pinning with wolfSSL
CVE-2025-5025 is fixed in curl on 1 platform, first by DEBIAN-CVE-2025-5025, released May 28, 2025. It is not reported as exploited. Patch Radar priority: Routine.
libcurl supports *pinning* of the server certificate public key for HTTPS transfers. Due to an omission, this check is not performed when connecting with QUIC for HTTP/3, when the TLS backend is wolfSSL. Documentation says the option works with wolfSSL, failing to specify that it does not for QUIC and HTTP/3. Since pinning makes the transfer succeed if the pin is fine, users could unwittingly connect to an impostor server without noticing.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| curl · Debian 13.5 (trixie) | 8.14.0-1 | DEBIAN-CVE-2025-5025 | May 28, 2025 |
| curl · Debian 14 | 8.14.0-1 | DEBIAN-CVE-2025-5025 | May 28, 2025 |
| curl · opensuse-leap 15.6 | 8.14.1-150600.4.28.1 | SUSE-SU-2025:03198-1 | Sep 12, 2025 |
| curl · sles 15.6 | 8.14.1-150600.4.28.1 | SUSE-SU-2025:03198-1 | Sep 12, 2025 |
| curl · sles 15.7 | 8.14.1-150600.4.28.1 | SUSE-SU-2025:03198-1 | Sep 12, 2025 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.