BlackTreeCVE Intelligencecurl · curl
Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · main | curl | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 8.14.0-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.22v3.22 · main | curl | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 8.14.0-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.21v3.21 · main | curl | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 8.14.0-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Debian trixietrixie · source | curl | Vendor fix publishedDebian records a fixed source-package version for this release. | 8.14.0-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | curl | Not affectedDebian marks this release not affected (fixed-version marker 0). | Not published in this feed | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | curl | Vendor fix publishedDebian records a fixed source-package version for this release. | 8.14.0-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | curl | Vendor fix publishedDebian records a fixed source-package version for this release. | 8.14.0-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
The vendor explicitly states that these products are not affected by this CVE.
Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Fix not verifiedlibcurl 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.
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.
The product does not validate, or incorrectly validates, a certificate.
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
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.
The product does not validate, or incorrectly validates, a certificate.
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.
CWE-295: Improper Certificate Validation. The product does not validate, or incorrectly validates, a certificate.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 28 May 2025 · Last source change 30 May 2025, 16:19 UTC · CWE-295 · Improper Certificate Validation
Core structured fields are present and their contributing authorities are shown above.
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.