BlackTreeCVE Intelligencecurl · curl
Official source article: Siemens SSA-398330 ↗. Check the applicable product and release in the original source.
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 5 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Verified remediation exists for at least one product or source, but 5 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
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. | 7.65.0-r0 | Alpine Security Database ↗Source updated 23 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. | 7.65.0-r0 | Alpine Security Database ↗Source updated 23 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. | 7.65.0-r0 | Alpine Security Database ↗Source updated 23 Oct 2026 |
| Debian trixietrixie · source | curl | Vendor fix publishedDebian records a fixed source-package version for this release. | 7.64.0-4 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
| Debian bookwormbookworm · source | curl | Vendor fix publishedDebian records a fixed source-package version for this release. | 7.64.0-4 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
| Debian forkyforky · source | curl | Vendor fix publishedDebian records a fixed source-package version for this release. | 7.64.0-4 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
| Debian sidsid · source | curl | Vendor fix publishedDebian records a fixed source-package version for this release. | 7.64.0-4 | Debian Security Tracker ↗Source updated 23 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 identifies these products as affected by this CVE.
The vendor explicitly identifies these products as affected by this CVE.
The vendor explicitly identifies these products as affected by this CVE.
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 5 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by productA heap buffer overflow in the TFTP receiving code allows for DoS or arbitrary code execution in libcurl versions 7.19.4 through 7.64.1.
A heap buffer overflow in the TFTP receiving code allows for DoS or arbitrary code execution in libcurl versions 7.19.4 through 7.64.1.
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.
A heap buffer overflow in the TFTP receiving code allows for DoS or arbitrary code execution in libcurl versions 7.19.4 through 7.64.1.
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.
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-122: Heap-based Buffer Overflow. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 28 May 2019 · Last source change 14 Oct 2026, 06:35 UTC · CWE-122 · Heap-based Buffer Overflow
Core structured fields are present and their contributing authorities are shown above.