CVE-2026-107928: When curl is built with GnuTLS, a malicious WebSocket server can make curl send memory past its send
Affects curlSource GCVE Database
Not known to be exploited · fixed in 8.20.0-2ubuntu11.1 : update curl when convenient.
Data as of 29 Oct 2026, 00:43 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- Patch
- Available – fixed in 8.20.0-2ubuntu11.1, 8.18.0-1ubuntu2.8
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade the Ubuntu curl to 8.20.0-2ubuntu11.1 (package) or 8.18.0-1ubuntu2.8 (package).
Patches and advisories
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10curlpkg:deb/ubuntu/curl?arch=source&distro=stonkingOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTScurlpkg:deb/ubuntu/curl?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix for this vulnerability is available in curl versions 8.20.0-2ubuntu11.1 and 8.18.0-1ubuntu2.8. Users should upgrade to these or later versions to mitigate the issue. No additional mitigation steps are required beyond applying the official patch.
Description
A vulnerability in curl built with GnuTLS allows a malicious WebSocket server to cause curl to send memory beyond its intended send buffer due to an out-of-bounds read. This occurs when gnutls_record_send() returns a byte count greater than the bytes requested to send after a blocked send. An attacker could exploit this to potentially obtain sensitive information. The issue affects specific Ubuntu package versions of curl and has been fixed in later releases.