CVE-2025-13034 | No QUIC certificate pinning with GnuTLS

When using `CURLOPT_PINNEDPUBLICKEY` option with libcurl or `--pinnedpubkey` with the curl tool,curl should check the public key of the server certificate to verify the peer. This check was skipped in a certain condition that would then make curl allow the connection without performing the proper check, thus not noticing a possible impostor. To skip this check, the connection had to be done with QUIC with ngtcp2 built to use GnuTLS and the user had to explicitly disable the standard certificate verification.

Published: 2026-01-08 Last update: 2026-01-20 Assigner: 2499f714-1537-4658-8207-48ae4bb9eae9 Source: 2499f714-1537-4658-8207-48ae4bb9eae9
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-13034 is rated Low Risk (28.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.23%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-13034

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.01% 0.23% +0.22%
2 2026-01-08 — 0.01% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-13034

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.9 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 2.2 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-13034

OS Trackers for CVE-2025-13034

vendor priority summary link
alpine — CVE-2025-13034: 1 source package rows (curl); 279 state rows across 6 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, 3.23-main, edge-main); fixed 67, open 212. https://security.alpinelinux.org/vuln/CVE-2025-13034
debian unimportant CVE-2025-13034 unimportant priority: Debian including 1 source packages (curl), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-13034
redhat medium — https://access.redhat.com/security/cve/CVE-2025-13034
suse medium CVE-2025-13034 severity moderate: SUSE including 7 source package names (curl, curl-zsh-completion, …), 141 product×package rows across 46 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (46 product lines)): Known Not Affected 141. https://www.suse.com/security/cve/CVE-2025-13034/
ubuntu medium CVE-2025-13034 medium priority: Ubuntu including 1 source packages (curl), 9 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): not-affected 6, released 2, ignored 1. https://ubuntu.com/security/CVE-2025-13034

Affected software / configurations for CVE-2025-13034

Vendor Product Version Raw CPE
haxx curl >= 8.8.0, < 8.18.0 cpe:2.3:a:haxx:curl:*:*:*:*:*:*:*:*

References for CVE-2025-13034

cvelogic Threat Intelligence