When using CURLOPT_PINNEDPUBLICKEY option with libcurl or --pinnedpubkey with the curl tool, curl should check the public key of the server… (CVE-2025-13034)
A vulnerability in curl's CURLOPT_PINNEDPUBLICKEY option allows skipping the public key check of the server certificate under specific conditions. This occurs when using QUIC with ngtcp2 built to use GnuTLS and when standard certificate verification is explicitly disabled by the user. This flaw could allow a connection to proceed without proper verification, potentially enabling a man-in-the-middle attack. The issue affects certain Ubuntu package versions of curl and has a medium severity rating with a CVSS score of 5.9. An official patch is available from Ubuntu to address this vulnerability.
AI Analysis
Technical Summary
CVE-2025-13034 describes a vulnerability in curl where the CURLOPT_PINNEDPUBLICKEY option or the --pinnedpubkey tool option fails to verify the server's public key under a specific condition. This condition requires the connection to be made using QUIC with ngtcp2 linked against GnuTLS and the user explicitly disabling standard certificate verification. Under these circumstances, curl skips the public key check, allowing connections to potentially an impostor server. The vulnerability was discovered by Stanislav Fort and affects several Ubuntu curl package versions. The issue is fixed in updated Ubuntu packages as per the Ubuntu security notice USN-8062-1.
Potential Impact
The vulnerability allows an attacker to bypass the pinned public key verification in curl, potentially enabling a man-in-the-middle attack if the user disables standard certificate verification and uses QUIC with ngtcp2 built with GnuTLS. This could lead to unauthorized interception or manipulation of data transmitted over the affected curl connections. The impact is limited by the requirement that the user must explicitly disable certificate verification and use a specific transport configuration.
Mitigation Recommendations
An official patch is available and should be applied by updating curl to the fixed versions provided by Ubuntu in security notice USN-8062-1. Users should avoid disabling standard certificate verification, especially when using QUIC with ngtcp2 and GnuTLS. Applying the vendor-provided updates will correct the issue and restore proper pinned public key verification.
When using CURLOPT_PINNEDPUBLICKEY option with libcurl or --pinnedpubkey with the curl tool, curl should check the public key of the server… (CVE-2025-13034)
Description
A vulnerability in curl's CURLOPT_PINNEDPUBLICKEY option allows skipping the public key check of the server certificate under specific conditions. This occurs when using QUIC with ngtcp2 built to use GnuTLS and when standard certificate verification is explicitly disabled by the user. This flaw could allow a connection to proceed without proper verification, potentially enabling a man-in-the-middle attack. The issue affects certain Ubuntu package versions of curl and has a medium severity rating with a CVSS score of 5.9. An official patch is available from Ubuntu to address this vulnerability.
CVSS v3.1
Score 5.9medium
Affected software
pkg:deb/ubuntu/curl?arch=source&distro=questingRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-13034 describes a vulnerability in curl where the CURLOPT_PINNEDPUBLICKEY option or the --pinnedpubkey tool option fails to verify the server's public key under a specific condition. This condition requires the connection to be made using QUIC with ngtcp2 linked against GnuTLS and the user explicitly disabling standard certificate verification. Under these circumstances, curl skips the public key check, allowing connections to potentially an impostor server. The vulnerability was discovered by Stanislav Fort and affects several Ubuntu curl package versions. The issue is fixed in updated Ubuntu packages as per the Ubuntu security notice USN-8062-1.
Potential Impact
The vulnerability allows an attacker to bypass the pinned public key verification in curl, potentially enabling a man-in-the-middle attack if the user disables standard certificate verification and uses QUIC with ngtcp2 built with GnuTLS. This could lead to unauthorized interception or manipulation of data transmitted over the affected curl connections. The impact is limited by the requirement that the user must explicitly disable certificate verification and use a specific transport configuration.
Mitigation Recommendations
An official patch is available and should be applied by updating curl to the fixed versions provided by Ubuntu in security notice USN-8062-1. Users should avoid disabling standard certificate verification, especially when using QUIC with ngtcp2 and GnuTLS. Applying the vendor-provided updates will correct the issue and restore proper pinned public key verification.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- UBUNTU-CVE-2025-13034
- Osv Schema Version
- 1.7.0
- Ecosystems
- ["Ubuntu:25.10"]
- Cvss Version
- 3.1
Patch Information
Threat ID: 6ab4be70f7a7c54106f0d454
Added to database: 09/24/2026, 06:08:48 UTC
Last enriched: 09/24/2026, 06:54:03 UTC
Last updated: 09/25/2026, 01:47:38 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.