<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T11:11:20.258004+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/bell-cve-2026-66034</id>
    <title>BELL-CVE-2026-66034</title>
    <updated>2026-09-30T11:11:23.128195+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: libssh2, Alpaquita:25: libssh2, Alpaquita:stream: libssh2</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/bell-cve-2026-66034"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/brew-libssh2-cve-2026-66034</id>
    <title>BREW-libssh2-CVE-2026-66034 — libssh2 Heap Out-of-Bounds Read via publickey subsystem</title>
    <updated>2026-09-30T11:11:23.128304+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: libssh2</p>
<p>libssh2 through 1.11.1, fixed in commit a13bb6c, contains a missing bounds check vulnerability that allows a malicious SSH server to trigger an arbitrary-length heap out-of-bounds read and a free of an uninitialized pointer via the publickey subsystem. In libssh2_publickey_list_fetch(), the version 1 response parser reads a server-controlled comment_len value and advances the parse pointer without verifying sufficient bytes remain in the buffer, causing the out-of-bounds read to leak heap pointers from adjacent allocations defeating ASLR, followed by heap allocator state corruption when the error cleanup path frees an uninitialized pointer from a non-zeroed realloc() region.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/brew-libssh2-cve-2026-66034"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-66034</id>
    <title>fkie_cve-2026-66034</title>
    <updated>2026-09-30T11:11:23.128363+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>libssh2 through 1.11.1, fixed in commit a13bb6c, contains a missing bounds check vulnerability that allows a malicious SSH server to trigger an arbitrary-length heap out-of-bounds read and a free of an uninitialized pointer via the publickey subsystem. In libssh2_publickey_list_fetch(), the version 1 response parser reads a server-controlled comment_len value and advances the parse pointer without verifying sufficient bytes remain in the buffer, causing the out-of-bounds read to leak heap pointers from adjacent allocations defeating ASLR, followed by heap allocator state corruption when the error cleanup path frees an uninitialized pointer from a non-zeroed realloc() region.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-66034"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-6h6q-9mwg-r6x7</id>
    <title>GHSA-6h6q-9mwg-r6x7</title>
    <updated>2026-09-30T11:11:23.128413+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>libssh2 through 1.11.1, fixed in commit a13bb6c, contains a missing bounds check vulnerability that allows a malicious SSH server to trigger an arbitrary-length heap out-of-bounds read and a free of an uninitialized pointer via the publickey subsystem. In libssh2_publickey_list_fetch(), the version 1 response parser reads a server-controlled comment_len value and advances the parse pointer without verifying sufficient bytes remain in the buffer, causing the out-of-bounds read to leak heap pointers from adjacent allocations defeating ASLR, followed by heap allocator state corruption when the error cleanup path frees an uninitialized pointer from a non-zeroed realloc() region.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-6h6q-9mwg-r6x7"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/msrc_cve-2026-66034</id>
    <title>msrc_CVE-2026-66034 — libssh2 Heap Out-of-Bounds Read via publickey subsystem</title>
    <updated>2026-09-30T11:11:23.128447+00:00</updated>
    <content>msrc_CVE-2026-66034</content>
    <link href="https://vulnerability.circl.lu/vuln/msrc_cve-2026-66034"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/oesa-2026-3392</id>
    <title>OESA-2026-3392 — libssh2 security update</title>
    <updated>2026-09-30T11:11:23.128479+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS-SP3: libssh2</p>
<p>libssh2 is a library implementing the SSH2 protocol as defined by Internet Drafts: SECSH-TRANS(22), SECSH-USERAUTH(25), SECSH-CONNECTION(23), SECSH-ARCH(20), SECSH-FILEXFER(06)*, SECSH-DHGEX(04), and SECSH-NUMBERS(10).

Security Fix(es):</p>
<p>libssh2 through 1.11.1 reads an attacker-controlled 32-bit attribute count from a publickey-subsystem response and uses it in the allocation num_attrs * sizeof(libssh2_publickey_attribute) without bounds checking, so on 32-bit platforms the multiplication overflows to an undersized buffer. A malicious SSH server can then drive the attribute-parsing loop to write past the allocation, causing a heap buffer overflow in a connecting libssh2 client.(CVE-2026-58050)</p>
<p>libssh2 through 1.11.1, fixed in commit 5e47761, contains a double-free vulnerability in the sftp_open() function in src/sftp.c that allows a malicious SSH server to corrupt the heap of any authenticated client opening an SFTP session. When a server responds to SSH_FXP_OPEN with SSH_FXP_STATUS containing FX_OK, the response data buffer is freed, and if a subsequent sftp_packet_require() call returns a specific error such as LIBSSH2_ERROR_CHANNEL_PACKET_EXCEEDED, the same pointer is freed a second time, enabling tcache dup conditions on glibc systems that allow overlapping allocations and function pointer overwrites.(CVE-2026-66032)</p>
<p>libssh2 through 1.11.1, fixed in commit a2ed82d, contains a pre-authentication integer underflow vulnerability in the ssh2_cipher_crypt() function in s…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/oesa-2026-3392"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11454-1</id>
    <title>openSUSE-SU-2026:11454-1 — libssh2-1-1.11.1-4.1 on GA media</title>
    <updated>2026-09-30T11:11:23.128573+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>libssh2-1-1.11.1-4.1 on GA media</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/opensuse-su-2026:11454-1"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/rhsa-2026:46927</id>
    <title>RHSA-2026:46927 — Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update</title>
    <updated>2026-09-30T11:11:23.128609+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>libssh2: libssh2: Denial of service or information disclosure via malformed SSH publickey response libssh2: libssh2: Arbitrary code execution via double-free in SFTP session libssh2: libssh2: Denial of Service via integer underflow in AES-GCM cipher negotiation libssh2: libssh2: Information disclosure and potential arbitrary code execution via heap out-of-bounds read</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/rhsa-2026:46927"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/suse-su-2026:23049-1</id>
    <title>SUSE-SU-2026:23049-1 — Security update for libssh2_org</title>
    <updated>2026-09-30T11:11:23.128650+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for libssh2_org</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/suse-su-2026:23049-1"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-66034</id>
    <title>UBUNTU-CVE-2026-66034</title>
    <updated>2026-09-30T11:11:23.128683+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: libssh2, Ubuntu:Pro:16.04:LTS: libssh2, Ubuntu:Pro:18.04:LTS: libssh2, Ubuntu:Pro:20.04:LTS: libssh2, Ubuntu:22.04:LTS: libssh2, Ubuntu:24.04:LTS: libssh2, Ubuntu:26.04:LTS: libssh2</p>
<p>libssh2 through 1.11.1, fixed in commit a13bb6c, contains a missing bounds check vulnerability that allows a malicious SSH server to trigger an arbitrary-length heap out-of-bounds read and a free of an uninitialized pointer via the publickey subsystem. In libssh2_publickey_list_fetch(), the version 1 response parser reads a server-controlled comment_len value and advances the parse pointer without verifying sufficient bytes remain in the buffer, causing the out-of-bounds read to leak heap pointers from adjacent allocations defeating ASLR, followed by heap allocator state corruption when the error cleanup path frees an uninitialized pointer from a non-zeroed realloc() region.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-66034"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2516</id>
    <title>WID-SEC-W-2026-2516 — libssh2: Mehrere Schwachstellen</title>
    <updated>2026-09-30T11:11:23.128742+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in libssh2 ausnutzen, um möglicherweise vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand herbeizuführen oder beliebigen Code auszuführen.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2516"/>
  </entry>
</feed>
