No QUIC certificate pinning with GnuTLS

Answer in brief

CVE-2025-13034 records a Unknown severity vulnerability in No QUIC certificate pinning with GnuTLS. The current sources do not mark it as known exploited. The current feed maps curl/curl (generic), curl/curl (generic), curl/curl (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Jan 8, 2026Updated Sep 15, 2026Source checked Sep 15, 2026First seen by HOL Sep 15, 2026Material review Sep 15, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 3 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps curl/curl (generic), curl/curl (generic), curl/curl (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
curl/curlgeneric	>=8.8.0 <8.14.2 \|\| >=8.15.0 <8.16.1 \|\| >=8.17.0 <8.18.0	8.14.2, 8.16.1, 8.18.0
curl/curlgeneric	>=3210101088dfa3d6a125d213226b092f2f866722 <3d91ca8cdb3b434226e743946d428b4dd3acf2c9	3d91ca8cdb3b434226e743946d428b4dd3acf2c9
curl/curlgeneric	8.17.0 \|\| 8.16.0 \|\| 8.15.0 \|\| 8.14.1 \|\| 8.14.0 \|\| 8.13.0 \|\| 8.12.1 \|\| 8.12.0 \|\| 8.11.1 \|\| 8.11.0 \|\| 8.10.1 \|\| 8.10.0 \|\| 8.9.1 \|\| 8.9.0 \|\| 8.8.0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for curl/curl, curl/curl, curl/curl.
Review the reported fix. Update curl/curl to 8.14.2; curl/curl to 3d91ca8cdb3b434226e743946d428b4dd3acf2c9 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Jan 8, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 15, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.