USN-8927-2 (UBUNTU-CVE-2026-86409)

Vulnerability from osv_ubuntu – Published: 2026-10-19 15:51 – Updated: 2026-10-19 15:51 – Source website
VLAI
Summary
curl vulnerabilities
Details

USN-8927-1 fixed vulnerabilities in curl. This update provides the corresponding fixes for Ubuntu 26.10.

Original advisory details:

It was discovered that curl, when built with GnuTLS support, had an out-of-bounds read in the WebSocket send path. An attacker could possibly use this issue to obtain sensitive information. (CVE-2026-107928)

Maksim discovered that curl did not correctly include the interface binding in connection reuse decisions when CURLOPT_INTERFACE was used. An attacker could possibly use this issue to cause connections to go out from an unintended source address. (CVE-2026-107929)

Stanislav Fort discovered that curl did not properly clear AWS SigV4 authentication state when CURLOPT_AWS_SIGV4 was set to NULL. An attacker could possibly use this issue to obtain sensitive information. (CVE-2026-86409)

Stanislav Fort discovered that the curl command line tool did not set SSH host verification options when following redirects to SFTP or SCP URLs. An attacker could possibly use this issue to perform machine-in-the-middle attacks. (CVE-2026-86410)

Stanislav Fort discovered that curl did not properly handle cookie jar entries that could not be reloaded. An attacker could possibly use this issue to cause a denial of service. (CVE-2026-86412)

Stanislav Fort discovered that an HTTP proxy could trick libcurl into sending credentials to the proxy itself by responding to a CONNECT request with an unexpected authentication challenge. An attacker could possibly use this issue to obtain sensitive information. (CVE-2026-86414)

Stanislav Fort discovered that curl did not correctly handle HSTS entries when an includeSubDomains parent entry was imported before a longer-lived child entry. An attacker could possibly use this issue to cause curl to use unencrypted HTTP connections. (CVE-2026-87862)

Stanislav Fort discovered that curl did not properly handle HSTS max-age values that exceeded calendar time structure bounds. An attacker could possibly use this issue to cause a denial of service or data loss. (CVE-2026-87863)

Stanislav Fort discovered that curl did not properly handle IMAP APPEND commands when CURLOPT_CRLF was enabled, allowing overflow bytes to be interpreted as pipelined commands. An authenticated attacker could possibly use this issue to inject arbitrary IMAP commands. (CVE-2026-87864)

Bobbeh Rhino discovered that libcurl, when used with libssh2 and a hashed known_hosts file, could misreport a host key mismatch as a missing key. An attacker could possibly use this issue to perform machine-in-the-middle attacks. (CVE-2026-87865)

Joshua Rogers discovered that curl did not properly handle long cookie entries written to a Netscape cookie jar. An attacker could possibly use this issue to cause a denial of service. (CVE-2026-92386)

Joshua Rogers discovered that a malicious FTP, IMAP, POP3, or SMTP server could cause libcurl to block indefinitely by omitting the final control-response line. An attacker could possibly use this issue to cause a denial of service. (CVE-2026-92387)

Joshua Rogers discovered that libcurl had a use-after-free vulnerability in the FTP wildcard matching code. An attacker could possibly use this issue to cause curl to crash, resulting in a denial of service, or execute arbitrary code. (CVE-2026-92388)

Joshua Rogers discovered that libcurl's TFTP state machine did not properly validate transfer directions, allowing a malicious server to force the client into transmit mode. An attacker could possibly use this issue to obtain sensitive information. (CVE-2026-92389)

Joshua Rogers discovered that curl did not properly enforce its file overwrite protection when using --remote-header-name in certain circumstances. An attacker could possibly use this issue to overwrite local files. (CVE-2026-92390)

Joshua Rogers discovered that curl had a stack overflow vulnerability when processing deeply nested MIME structures. An attacker could possibly use this issue to cause curl to crash, resulting in a denial of service. (CVE-2026-92391)

Joshua Rogers discovered that libcurl could expose credentials in the URL returned by CURLINFO_EFFECTIVE_URL when credentials were retrieved from a .netrc file. An attacker could possibly use this issue to obtain sensitive information. (CVE-2026-94266)

Joshua Rogers discovered that libcurl had a use-after-free vulnerability during HTTP/2 uploads when handling RST_STREAM responses from the server. An attacker could possibly use this issue to cause curl to crash, resulting in a denial of service, or execute arbitrary code. (CVE-2026-92392)

References
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "cves_map": {
          "cves": [
            {
              "id": "CVE-2026-86409",
              "severity": [
                {
                  "score": "low",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2026-86410",
              "severity": [
                {
                  "score": "low",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2026-86412",
              "severity": [
                {
                  "score": "low",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2026-86414",
              "severity": [
                {
                  "score": "low",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2026-87862",
              "severity": [
                {
                  "score": "low",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2026-87863",
              "severity": [
                {
                  "score": "low",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2026-87864",
              "severity": [
                {
                  "score": "low",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2026-87865",
              "severity": [
                {
                  "score": "low",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2026-92386",
              "severity": [
                {
                  "score": "low",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2026-92387",
              "severity": [
                {
                  "score": "low",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2026-92388",
              "severity": [
                {
                  "score": "low",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2026-92389",
              "severity": [
                {
                  "score": "low",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2026-92390",
              "severity": [
                {
                  "score": "low",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2026-92391",
              "severity": [
                {
                  "score": "low",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "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": [
                {
                  "score": "low",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2026-107929",
              "severity": [
                {
                  "score": "low",
                  "type": "Ubuntu"
                }
              ]
            }
          ],
          "ecosystem": "Ubuntu:26.10"
        }
      },
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "curl",
            "binary_version": "8.20.0-2ubuntu11.1"
          },
          {
            "binary_name": "libcurl3t64-gnutls",
            "binary_version": "8.20.0-2ubuntu11.1"
          },
          {
            "binary_name": "libcurl4t64",
            "binary_version": "8.20.0-2ubuntu11.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:26.10",
        "name": "curl",
        "purl": "pkg:deb/ubuntu/curl@8.20.0-2ubuntu11.1?arch=source\u0026distro=stonking"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "8.20.0-2ubuntu11.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "8.18.0-1ubuntu2",
        "8.20.0-2ubuntu1",
        "8.20.0-2ubuntu3",
        "8.20.0-2ubuntu10",
        "8.20.0-2ubuntu11"
      ]
    }
  ],
  "aliases": [],
  "details": "USN-8927-1 fixed vulnerabilities in curl. This update provides the\ncorresponding fixes for Ubuntu 26.10.\n\nOriginal advisory details:\n\n It was discovered that curl, when built with GnuTLS support, had an\n out-of-bounds read in the WebSocket send path. An attacker could\n possibly use this issue to obtain sensitive information.\n (CVE-2026-107928)\n\n Maksim discovered that curl did not correctly include the interface\n binding in connection reuse decisions when CURLOPT_INTERFACE was used.\n An attacker could possibly use this issue to cause connections to go\n out from an unintended source address. (CVE-2026-107929)\n\n Stanislav Fort discovered that curl did not properly clear AWS SigV4\n authentication state when CURLOPT_AWS_SIGV4 was set to NULL. An\n attacker could possibly use this issue to obtain sensitive information.\n (CVE-2026-86409)\n\n Stanislav Fort discovered that the curl command line tool did not set\n SSH host verification options when following redirects to SFTP or SCP\n URLs. An attacker could possibly use this issue to perform\n machine-in-the-middle attacks. (CVE-2026-86410)\n\n Stanislav Fort discovered that curl did not properly handle cookie jar\n entries that could not be reloaded. An attacker could possibly use this\n issue to cause a denial of service. (CVE-2026-86412)\n\n Stanislav Fort discovered that an HTTP proxy could trick libcurl into\n sending credentials to the proxy itself by responding to a CONNECT\n request with an unexpected authentication challenge. An attacker could\n possibly use this issue to obtain sensitive information.\n (CVE-2026-86414)\n\n Stanislav Fort discovered that curl did not correctly handle HSTS\n entries when an includeSubDomains parent entry was imported before a\n longer-lived child entry. An attacker could possibly use this issue to\n cause curl to use unencrypted HTTP connections. (CVE-2026-87862)\n\n Stanislav Fort discovered that curl did not properly handle HSTS\n max-age values that exceeded calendar time structure bounds. An\n attacker could possibly use this issue to cause a denial of service or\n data loss. (CVE-2026-87863)\n\n Stanislav Fort discovered that curl did not properly handle IMAP APPEND\n commands when CURLOPT_CRLF was enabled, allowing overflow bytes to be\n interpreted as pipelined commands. An authenticated attacker could\n possibly use this issue to inject arbitrary IMAP commands.\n (CVE-2026-87864)\n\n Bobbeh Rhino discovered that libcurl, when used with libssh2 and a\n hashed known_hosts file, could misreport a host key mismatch as a\n missing key. An attacker could possibly use this issue to perform\n machine-in-the-middle attacks. (CVE-2026-87865)\n\n Joshua Rogers discovered that curl did not properly handle long cookie\n entries written to a Netscape cookie jar. An attacker could possibly\n use this issue to cause a denial of service. (CVE-2026-92386)\n\n Joshua Rogers discovered that a malicious FTP, IMAP, POP3, or SMTP\n server could cause libcurl to block indefinitely by omitting the final\n control-response line. An attacker could possibly use this issue to\n cause a denial of service. (CVE-2026-92387)\n\n Joshua Rogers discovered that libcurl had a use-after-free\n vulnerability in the FTP wildcard matching code. An attacker could\n possibly use this issue to cause curl to crash, resulting in a denial\n of service, or execute arbitrary code. (CVE-2026-92388)\n\n Joshua Rogers discovered that libcurl\u0027s TFTP state machine did not\n properly validate transfer directions, allowing a malicious server to\n force the client into transmit mode. An attacker could possibly use\n this issue to obtain sensitive information. (CVE-2026-92389)\n\n Joshua Rogers discovered that curl did not properly enforce its file\n overwrite protection when using --remote-header-name in certain\n circumstances. An attacker could possibly use this issue to overwrite\n local files. (CVE-2026-92390)\n\n Joshua Rogers discovered that curl had a stack overflow vulnerability\n when processing deeply nested MIME structures. An attacker could\n possibly use this issue to cause curl to crash, resulting in a denial\n of service. (CVE-2026-92391)\n\n Joshua Rogers discovered that libcurl could expose credentials in the\n URL returned by CURLINFO_EFFECTIVE_URL when credentials were retrieved\n from a .netrc file. An attacker could possibly use this issue to obtain\n sensitive information. (CVE-2026-94266)\n\n Joshua Rogers discovered that libcurl had a use-after-free\n vulnerability during HTTP/2 uploads when handling RST_STREAM responses\n from the server. An attacker could possibly use this issue to cause\n curl to crash, resulting in a denial of service, or execute arbitrary\n code. (CVE-2026-92392)",
  "id": "USN-8927-2",
  "modified": "2026-10-19T15:51:17Z",
  "published": "2026-10-19T15:51:17Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-8927-2"
    },
    {
      "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"
    }
  ],
  "related": [],
  "schema_version": "1.7.0",
  "summary": "curl vulnerabilities",
  "upstream": [
    "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",
    "UBUNTU-CVE-2026-107928",
    "UBUNTU-CVE-2026-107929"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.