Updated openssh packages fix security vulnerabilities
Publication date: 19 Oct 2026Modification date: 19 Oct 2026
Type: security
Affected Mageia releases : 10
CVE: CVE-2026-55655 , CVE-2026-59995 , CVE-2026-59996 , CVE-2026-59997 , CVE-2026-59998 , CVE-2026-59999 , CVE-2026-60000 , CVE-2026-60001 , CVE-2026-60002 , CVE-2026-73281 , CVE-2026-73282 , CVE-2026-73283 , CVE-2026-106552 , CVE-2026-106553 , CVE-2026-106555 , CVE-2026-106582 , CVE-2026-106583 , CVE-2026-106584 , CVE-2026-106585 , CVE-2026-106586 , CVE-2026-106587
Description
Local mitm of x11 forwarding via abstract unix socket pre-binding in Red
Hat Enterprise Linux openssh client versions. (CVE-2026-55655)
sftp in OpenSSH before 10.4 does not properly constrain the location of
downloaded files when "sftp server:/path ." is used with an
attacker-controlled server. (CVE-2026-59995)
scp in OpenSSH before 10.4 may place a file in the parent directory of
an intended directory when the copy occurs between two remote
destinations. (CVE-2026-59996)
internal-sftp in sshd in OpenSSH before 10.4 recognizes only the first 9
command-line arguments, which can be important if a later command-line
argument would have helped to ensure the intended security properties of
an SFTP connection. (CVE-2026-59997)
sshd in OpenSSH before 10.4 has an undocumented security-relevant
behavior: GSSAPIStrictAcceptorCheck has no value if the server is in
Windows Active Directory. (CVE-2026-59998)
In sshd in OpenSSH before 10.4, DisableForwarding=yes was supposed to
take precedence over PermitTunnel=yes, but did not. (CVE-2026-59999)
sshd in OpenSSH before 10.4 allows remote attackers to cause a denial of
service (resource consumption from excessive authentication attempts)
because MaxAuthTries was mishandled for GSSAPIAuthentication.
(CVE-2026-60000)
sshd in OpenSSH before 10.4 does not always honor the minimum
authentication delay. (CVE-2026-60001)
ssh in OpenSSH before 10.4 can have a use-after-free when a server
changes its host key during a key re-exchange. (This outcome occurs only
on the client side.). (CVE-2026-60002)
In ssh-agent in OpenSSH before 10.5, some operations can occur remotely
but were intended to occur only locally, including operations that add
tokens or use keys. This is caused by misinteraction between agent
locking and the session-bind@openssh.com extension. (CVE-2026-73281)
In ssh in OpenSSH before 10.5, a use-after-free for realloc data can
occur if a certain pair of remote-forwarding operations are concurrent.
(CVE-2026-73282)
In sshd in OpenSSH before 10.5, the restrict keyword (in
authorized_keys) was supposed to be applicable to tunnel forwarding but
was not. (CVE-2026-73283)
In sftp in OpenSSH before 10.6, a server can trigger directory traversal
(causing files to be written to unintended locations) during a recursive
copy operation. (CVE-2026-106552)
In sshd in OpenSSH before 10.6, credentials can incorrectly persist
after failure of a GSSAPIAuthentication authentication attempt.
(CVE-2026-106553)
In sshd in OpenSSH before 10.6, GSSAPIAuthentication authentication
state can incorrectly be persisted across authentication attempts.
(CVE-2026-106555)
In sshd and ssh in OpenSSH before 10.6, an LZ77 dictionary coder can be
used even though this is contraindicated by the arXiv 2609.07709
"Crossing the Streams" findings. (CVE-2026-106582)
In ssh in OpenSSH before 10.6, a $ or \ character can occur in a
command-line username, leading to injection. (CVE-2026-106583)
In ssh-keygen in OpenSSH before 10.6, certificates could have incorrect
expiration times because of Daylight Saving mishandling. There can be a
slightly more severe effect on users in certain Antarctic locations.
(CVE-2026-106584)
In sshd and ssh in OpenSSH before 10.6, there is no check for whether
the maximum packet length is exceeded during decompression of highly
compressed data. (CVE-2026-106585)
In sshd in OpenSSH before 10.6, the restrict keyword (in
authorized_keys) was supposed to be applicable to tunnel forwarding but
was not, a different vulnerability than CVE-2026-73283.
(CVE-2026-106586)
In sshd in OpenSSH before 10.6, the value "none" for a configuration
option is sometimes interpreted as a filename but was intended to mean
that a feature is disabled. (CVE-2026-106587)
References
- https://bugs.mageia.org/show_bug.cgi?id=35876
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5FAMKD5T6664L7TA7EBJFLZB2RX3AQYZ/
- https://ubuntu.com/security/notices/USN-8533-1
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/I2ZK2T3OFPOIBFAZQAJISQ7EML4PHYVB/
- https://www.openwall.com/lists/oss-security/2026/08/12/1
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YRB2YTKIEJGFGAKEXYAPCDQSKUFBEI7B/
- https://ubuntu.com/security/notices/USN-8721-1
- https://ubuntu.com/security/notices/USN-8928-1
- https://www.cve.org/CVERecord?id=CVE-2026-55655
- https://www.cve.org/CVERecord?id=CVE-2026-59995
- https://www.cve.org/CVERecord?id=CVE-2026-59996
- https://www.cve.org/CVERecord?id=CVE-2026-59997
- https://www.cve.org/CVERecord?id=CVE-2026-59998
- https://www.cve.org/CVERecord?id=CVE-2026-59999
- https://www.cve.org/CVERecord?id=CVE-2026-60000
- https://www.cve.org/CVERecord?id=CVE-2026-60001
- https://www.cve.org/CVERecord?id=CVE-2026-60002
- https://www.cve.org/CVERecord?id=CVE-2026-73281
- https://www.cve.org/CVERecord?id=CVE-2026-73282
- https://www.cve.org/CVERecord?id=CVE-2026-73283
- https://www.cve.org/CVERecord?id=CVE-2026-106552
- https://www.cve.org/CVERecord?id=CVE-2026-106553
- https://www.cve.org/CVERecord?id=CVE-2026-106555
- https://www.cve.org/CVERecord?id=CVE-2026-106582
- https://www.cve.org/CVERecord?id=CVE-2026-106583
- https://www.cve.org/CVERecord?id=CVE-2026-106584
- https://www.cve.org/CVERecord?id=CVE-2026-106585
- https://www.cve.org/CVERecord?id=CVE-2026-106586
- https://www.cve.org/CVERecord?id=CVE-2026-106587
SRPMS
10/core
- openssh-10.0p1-4.1.mga10