OpenSSH vulnerabilities and fixes

CVEs that mention OpenSSH, ranked by priority. 4 tracked.

OpenSSH has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2026-10-21. Highest priority: CVE-2026-73282 (score 28/100).

• CVE-2026-73282 MEDIUM 4.8 UPGRADE In ssh in OpenSSH before 10.5, a use-after-free for realloc data can occur if a certain pair of remote-forward
• CVE-2026-73281 LOW 3.5 UPGRADE In ssh-agent in OpenSSH before 10.5, some operations can occur remotely but were intended to occur only locall
• CVE-2026-73283 LOW 2.5 UPGRADE In sshd in OpenSSH before 10.5, the restrict keyword (in authorized_keys) was supposed to be applicable to tun
• CVE-2026-94140 HIGH n/a Rex versions through 1.16.1 for Perl accept an unknown SSH host key for remote rsync transfers because sync ha

FAQ

How do I fix OpenSSH vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is OpenSSH being exploited right now?

None of the tracked OpenSSH CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which OpenSSH CVE should I patch first?

CVE-2026-73282 currently ranks highest (28/100): In ssh in OpenSSH before 10.5, a use-after-free for realloc data can occur if a certain pair of remote-forward.

← Back to latest CVEs