{"id":"USN-8927-1","summary":"curl vulnerabilities","details":"It was discovered that curl, when built with GnuTLS support, had an\nout-of-bounds read in the WebSocket send path. An attacker could\npossibly use this issue to obtain sensitive information.\n(CVE-2026-107928)\n\nMaksim discovered that curl did not correctly include the interface\nbinding in connection reuse decisions when CURLOPT_INTERFACE was used.\nAn attacker could possibly use this issue to cause connections to go\nout from an unintended source address. (CVE-2026-107929)\n\nStanislav Fort discovered that curl did not properly clear AWS SigV4\nauthentication state when CURLOPT_AWS_SIGV4 was set to NULL. An\nattacker could possibly use this issue to obtain sensitive information.\n(CVE-2026-86409)\n\nStanislav Fort discovered that the curl command line tool did not set\nSSH host verification options when following redirects to SFTP or SCP\nURLs. An attacker could possibly use this issue to perform\nmachine-in-the-middle attacks. (CVE-2026-86410)\n\nStanislav Fort discovered that curl did not properly handle cookie jar\nentries that could not be reloaded. An attacker could possibly use this\nissue to cause a denial of service. (CVE-2026-86412)\n\nStanislav Fort discovered that an HTTP proxy could trick libcurl into\nsending credentials to the proxy itself by responding to a CONNECT\nrequest with an unexpected authentication challenge. An attacker could\npossibly use this issue to obtain sensitive information.\n(CVE-2026-86414)\n\nStanislav Fort discovered that curl did not correctly handle HSTS\nentries when an includeSubDomains parent entry was imported before a\nlonger-lived child entry. An attacker could possibly use this issue to\ncause curl to use unencrypted HTTP connections. (CVE-2026-87862)\n\nStanislav Fort discovered that curl did not properly handle HSTS\nmax-age values that exceeded calendar time structure bounds. An\nattacker could possibly use this issue to cause a denial of service or\ndata loss. (CVE-2026-87863)\n\nStanislav Fort discovered that curl did not properly handle IMAP APPEND\ncommands when CURLOPT_CRLF was enabled, allowing overflow bytes to be\ninterpreted as pipelined commands. An authenticated attacker could\npossibly use this issue to inject arbitrary IMAP commands.\n(CVE-2026-87864)\n\nBobbeh Rhino discovered that libcurl, when used with libssh2 and a\nhashed known_hosts file, could misreport a host key mismatch as a\nmissing key. An attacker could possibly use this issue to perform\nmachine-in-the-middle attacks. (CVE-2026-87865)\n\nJoshua Rogers discovered that curl did not properly handle long cookie\nentries written to a Netscape cookie jar. An attacker could possibly\nuse this issue to cause a denial of service. (CVE-2026-92386)\n\nJoshua Rogers discovered that a malicious FTP, IMAP, POP3, or SMTP\nserver could cause libcurl to block indefinitely by omitting the final\ncontrol-response line. An attacker could possibly use this issue to\ncause a denial of service. (CVE-2026-92387)\n\nJoshua Rogers discovered that libcurl had a use-after-free\nvulnerability in the FTP wildcard matching code. An attacker could\npossibly use this issue to cause curl to crash, resulting in a denial\nof service, or execute arbitrary code. (CVE-2026-92388)\n\nJoshua Rogers discovered that libcurl's TFTP state machine did not\nproperly validate transfer directions, allowing a malicious server to\nforce the client into transmit mode. An attacker could possibly use\nthis issue to obtain sensitive information. (CVE-2026-92389)\n\nJoshua Rogers discovered that curl did not properly enforce its file\noverwrite protection when using --remote-header-name in certain\ncircumstances. An attacker could possibly use this issue to overwrite\nlocal files. (CVE-2026-92390)\n\nJoshua Rogers discovered that curl had a stack overflow vulnerability\nwhen processing deeply nested MIME structures. An attacker could\npossibly use this issue to cause curl to crash, resulting in a denial\nof service. (CVE-2026-92391)\n\nJoshua Rogers discovered that libcurl could expose credentials in the\nURL returned by CURLINFO_EFFECTIVE_URL when credentials were retrieved\nfrom a .netrc file. An attacker could possibly use this issue to obtain\nsensitive information. (CVE-2026-94266)\n\nJoshua Rogers discovered that libcurl had a use-after-free\nvulnerability during HTTP/2 uploads when handling RST_STREAM responses\nfrom the server. An attacker could possibly use this issue to cause\ncurl to crash, resulting in a denial of service, or execute arbitrary\ncode. (CVE-2026-92392)","modified":"2026-10-17T13:12:59.609211919Z","published":"2026-10-14T11:58:06Z","related":["UBUNTU-CVE-2026-107928","UBUNTU-CVE-2026-107929","UBUNTU-CVE-2026-86409","UBUNTU-CVE-2026-86410","UBUNTU-CVE-2026-86412","UBUNTU-CVE-2026-86414","UBUNTU-CVE-2026-87862","UBUNTU-CVE-2026-87863","UBUNTU-CVE-2026-87864","UBUNTU-CVE-2026-87865","UBUNTU-CVE-2026-92386","UBUNTU-CVE-2026-92387","UBUNTU-CVE-2026-92388","UBUNTU-CVE-2026-92389","UBUNTU-CVE-2026-92390","UBUNTU-CVE-2026-92391","UBUNTU-CVE-2026-92392","UBUNTU-CVE-2026-94266"],"upstream":["CVE-2026-107928","CVE-2026-107929","CVE-2026-86409","CVE-2026-86410","CVE-2026-86412","CVE-2026-86414","CVE-2026-87862","CVE-2026-87863","CVE-2026-87864","CVE-2026-87865","CVE-2026-92386","CVE-2026-92387","CVE-2026-92388","CVE-2026-92389","CVE-2026-92390","CVE-2026-92391","CVE-2026-92392","CVE-2026-94266","UBUNTU-CVE-2026-107928","UBUNTU-CVE-2026-107929","UBUNTU-CVE-2026-86409","UBUNTU-CVE-2026-86410","UBUNTU-CVE-2026-86412","UBUNTU-CVE-2026-86414","UBUNTU-CVE-2026-87862","UBUNTU-CVE-2026-87863","UBUNTU-CVE-2026-87864","UBUNTU-CVE-2026-87865","UBUNTU-CVE-2026-92386","UBUNTU-CVE-2026-92387","UBUNTU-CVE-2026-92388","UBUNTU-CVE-2026-92389","UBUNTU-CVE-2026-92390","UBUNTU-CVE-2026-92391","UBUNTU-CVE-2026-92392","UBUNTU-CVE-2026-94266"],"references":[{"type":"ADVISORY","url":"https://ubuntu.com/security/notices/USN-8927-1"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2026-86409"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2026-86410"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2026-86412"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2026-86414"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2026-87862"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2026-87863"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2026-87864"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2026-87865"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2026-92386"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2026-92387"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2026-92388"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2026-92389"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2026-92390"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2026-92391"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2026-92392"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2026-94266"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2026-107928"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2026-107929"}],"affected":[{"package":{"name":"curl","ecosystem":"Ubuntu:26.04:LTS","purl":"pkg:deb/ubuntu/curl?arch=source&distro=resolute"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.18.0-1ubuntu2.8"}]}],"versions":["8.14.1-2ubuntu1","8.17.0-1ubuntu1","8.18.0-1ubuntu1","8.18.0-1ubuntu2","8.18.0-1ubuntu2.1","8.18.0-1ubuntu2.2","8.18.0-1ubuntu2.3","8.18.0-1ubuntu2.4","8.18.0-1ubuntu2.5","8.18.0-1ubuntu2.7"],"ecosystem_specific":{"binaries":[{"binary_version":"8.18.0-1ubuntu2.8","binary_name":"curl"},{"binary_name":"libcurl3t64-gnutls","binary_version":"8.18.0-1ubuntu2.8"},{"binary_name":"libcurl4t64","binary_version":"8.18.0-1ubuntu2.8"}],"availability":"No subscription required"},"database_specific":{"source":"https://github.com/canonical/ubuntu-security-notices/blob/main/osv/usn/USN-8927-1.json","cves_map":{"cves":[{"id":"CVE-2026-86409","severity":[{"type":"Ubuntu","score":"low"}]},{"id":"CVE-2026-86410","severity":[{"type":"Ubuntu","score":"low"}]},{"id":"CVE-2026-86412","severity":[{"type":"Ubuntu","score":"low"}]},{"severity":[{"type":"Ubuntu","score":"low"}],"id":"CVE-2026-86414"},{"severity":[{"type":"Ubuntu","score":"low"}],"id":"CVE-2026-87862"},{"id":"CVE-2026-87863","severity":[{"type":"Ubuntu","score":"low"}]},{"severity":[{"type":"Ubuntu","score":"low"}],"id":"CVE-2026-87864"},{"id":"CVE-2026-87865","severity":[{"type":"Ubuntu","score":"low"}]},{"id":"CVE-2026-92386","severity":[{"score":"low","type":"Ubuntu"}]},{"severity":[{"type":"Ubuntu","score":"low"}],"id":"CVE-2026-92387"},{"severity":[{"score":"low","type":"Ubuntu"}],"id":"CVE-2026-92388"},{"id":"CVE-2026-92389","severity":[{"type":"Ubuntu","score":"low"}]},{"id":"CVE-2026-92390","severity":[{"type":"Ubuntu","score":"low"}]},{"severity":[{"type":"Ubuntu","score":"low"}],"id":"CVE-2026-92391"},{"id":"CVE-2026-92392","severity":[{"score":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","type":"CVSS_V3"},{"score":"high","type":"Ubuntu"}]},{"id":"CVE-2026-94266","severity":[{"score":"low","type":"Ubuntu"}]},{"id":"CVE-2026-107928","severity":[{"type":"Ubuntu","score":"low"}]},{"id":"CVE-2026-107929","severity":[{"score":"low","type":"Ubuntu"}]}],"ecosystem":"Ubuntu:26.04:LTS"}}}],"schema_version":"1.9.0"}