Описание
A flaw was found in libssh. Incorrect AES-GCM finalization checks in builds using the OpenSSL backend can effectively remove integrity protection, allowing an in-path attacker to modify plaintext on the wire without detection.
A flaw was found in libssh. Incorrect AES-GCM finalization checks in builds using the OpenSSL backend can effectively remove integrity protection, allowing an in-path attacker to modify plaintext on the wire without detection.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2026-59847
- https://access.redhat.com/errata/RHSA-2026:42922
- https://access.redhat.com/errata/RHSA-2026:55855
- https://access.redhat.com/errata/RHSA-2026:62217
- https://access.redhat.com/errata/RHSA-2026:62218
- https://access.redhat.com/security/cve/CVE-2026-59847
- https://bugzilla.redhat.com/show_bug.cgi?id=2498180
Связанные уязвимости
A flaw was found in libssh. Incorrect AES-GCM finalization checks in builds using the OpenSSL backend can effectively remove integrity protection, allowing an in-path attacker to modify plaintext on the wire without detection.
A flaw was found in libssh. Incorrect AES-GCM finalization checks in builds using the OpenSSL backend can effectively remove integrity protection, allowing an in-path attacker to modify plaintext on the wire without detection.
A flaw was found in libssh. Incorrect AES-GCM finalization checks in builds using the OpenSSL backend can effectively remove integrity protection, allowing an in-path attacker to modify plaintext on the wire without detection.
Libssh: libssh: integrity downgrade via openssl aes-gcm tag verification
A flaw was found in libssh. Incorrect AES-GCM finalization checks in b ...