p PatchFirst

PatchFirst · Vulnérabilités récentes

openssh 10.4 : vulnérabilités connues

Vulnérabilités connues concernant openssh 10.4 : 14. Comparez les versions corrigées ci-dessous avec celle que vous utilisez.

RSS ↗
Filtrer les vulnérabilités
Effacer les filtres

Vulnérabilités : 14

  1. CVE-2026-106589

    Faible · CVSS 2.9EPSS 0,08%Aucun correctif publié

    CVE-2026-106589

    In sshd in OpenSSH through 10.6, in certain environments such as QNX 6 and SCO OpenServer 5, sshd-session can unexpectedly have root privileges. This is related to the GatewayPorts and StreamLocalForwarding configuration options, and lack of support for file-descriptor passing and unprivileged allocation of PTY devices.

    Publication Mise à jour
  2. CVE-2026-106587

    Faible · CVSS 3.6EPSS 0,08%Correctif disponible

    CVE-2026-106587

    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.

    • Mettez à jour vers 10.6
    Publication Mise à jour
  3. CVE-2026-106586

    Faible · CVSS 2.5EPSS 0,12%Correctif disponible

    CVE-2026-106586

    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.

    • Mettez à jour vers 10.6
    Publication Mise à jour
  4. CVE-2026-106584

    Faible · CVSS 2.5EPSS 0,06%Correctif disponible

    CVE-2026-106584

    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.

    • Mettez à jour vers 10.6
    Publication Mise à jour
  5. CVE-2026-73281

    Faible · CVSS 3.5EPSS 0,16%Correctif disponible

    CVE-2026-73281

    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 [email protected] extension.

    • Mettez à jour vers 10.5
    Publication Mise à jour

Vérifiez votre serveur

Comparez votre pile et les versions installées aux bases de vulnérabilités actuelles.

Vérifiez votre serveur →