Skip to content
Connect AISign inSign up free
CVE-2025-50254.8MediumCWE-295

CVE-2025-5025: No QUIC certificate pinning with wolfSSL

curl

Affected: curl · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.3%probability of exploitation in the next 30 days
23rd percentile
050100

Higher than 23% of scored CVEs

4.8MediumCVSS 3.1
LowMedium

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • curl · curlfrom 8.13.0 up to and including 8.13.0; from 8.12.1 up to and including 8.12.1; from 8.12.0 up to and including 8.12.0; from 8.11.1 up to and including 8.11.1; from 8.11.0 up to and including 8.11.0; from 8.10.1 up to and including 8.10.1 and 8 more

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
curl
Published
May 2025

Disclosed bug bounty reports about CVE-2025-5025

The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.

CoverageNo articles yet

No CyberSIXT article names CVE-2025-5025 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References