Bug 2507310 - CVE-2026-66034 mingw-libssh2: libssh2: Information disclosure and potential arbitrary code execution via heap out-of-bounds read [fedora-all]
Summary: CVE-2026-66034 mingw-libssh2: libssh2: Information disclosure and potential a...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: mingw-libssh2
Version: 45
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Michael Cronenworth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["191a776d-7f28-425d-bb24-0...
Depends On:
Blocks: CVE-2026-66034
TreeView+ depends on / blocked
 
Reported: 2026-07-25 14:52 UTC by Srikanth Balasubramanian
Modified: 2026-08-17 15:37 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Srikanth Balasubramanian 2026-07-25 14:52:07 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

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.

Comment 1 Aoife Moloney 2026-08-17 15:37:15 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 45 development cycle.
Changing version to 45.


Note You need to log in before you can comment on or make changes to this bug.