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.
{
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/5xxx/CVE-2025-5025.json",
"cna_assigner": "curl",
"unresolved_ranges": [
{
"extracted_events": [
{
"last_affected": "8.13.0"
},
{
"last_affected": "8.12.1"
},
{
"last_affected": "8.12.0"
},
{
"last_affected": "8.11.1"
},
{
"last_affected": "8.11.0"
},
{
"last_affected": "8.10.1"
},
{
"last_affected": "8.10.0"
},
{
"last_affected": "8.9.1"
},
{
"last_affected": "8.9.0"
},
{
"last_affected": "8.8.0"
},
{
"last_affected": "8.7.1"
},
{
"last_affected": "8.7.0"
},
{
"last_affected": "8.6.0"
},
{
"last_affected": "8.5.0"
}
],
"source": "AFFECTED_FIELD"
}
]
}