Loading story…
A cryptographic implementation review of Go's golang.org/x/crypto/ssh package found 15 issues and led to coordinated fixes for nine CVEs affecting SSH client and server functionality. NCC Group said the assessment, commissioned by Teleport in early 2026, concluded that the codebase was generally well structured and documented but uncovered security flaws including certificate restriction bypasses, denial-of-service conditions, deadlocks, infinite loops, panics, and failures in SSH agent constraint enforcement.
The vulnerabilities were remediated with the release of golang.org/x/crypto version v0.52.0, which was published on May 22, 2026, alongside an announcement to the Golang Announce group. The review also noted that any future post-quantum cryptography support in x/crypto/ssh should be implemented carefully within the package's existing framework to avoid introducing new weaknesses.
See affected versions and whether adversaries are exploiting it.
4 events from the most recent confirmed update back to the earliest known activity.
The x/crypto v0.52.0 release containing the SSH fixes was announced on the Golang Announce group after the coordinated remediation effort.
The identified issues were remediated in golang.org/x/crypto version 0.52.0, which addressed the vulnerabilities found in the x/crypto/ssh review.
During the review, NCC Group documented 15 findings in x/crypto/ssh and related components, leading to nine filed CVEs covering certificate restriction bypasses, denial-of-service conditions, deadlocks, infinite loops, panics, and SSH agent constraint enforcement failures.
In early 2026, Teleport engaged NCC Group's Cryptography Services practice to review the Go x/crypto/ssh package, with Geomys providing technical support and coordinating remediation and disclosure.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
OpenSSH has released **version 10.4** with eight security fixes affecting both client and server components, including `sftp`, `scp`, `sshd`, `ssh`, `ssh-agent`, and cryptographic verification logic. The update addresses path traversal-style and file redirection issues that could let a malicious server write files outside intended locations, a **pre-authentication denial-of-service** condition in `sshd`, a client-side **use-after-free** bug, and gaps in authentication delay enforcement. The release also replaces the wildcard matcher with an NFA-based implementation to remove exponential worst-case behavior. The release introduces experimental support for a composite post-quantum signature scheme combining **ML-DSA 44** with **Ed25519**, available only when explicitly enabled and configured. OpenSSH also hardened protocol handling by disconnecting peers that send non-KEX messages during post-authentication rekeying and made seccomp sandbox initialization failures fatal on Linux. Maintainers warned that some changes may break existing deployments, including mixed-case output from `sshd -G`, stricter transport-layer behavior, and the new sandbox failure handling.
Jul 12, 2026
Go disclosed **CVE-2026-32283**, an Important denial-of-service flaw in `crypto/tls` that can deadlock TLS 1.3 connections when a peer sends multiple post-handshake key update messages in a single record, leading to uncontrolled resource consumption. Go also disclosed **CVE-2026-27144** in `cmd/compile`, where a no-op interface conversion could bypass overlap checks for memory moves, creating conditions for unsafe overlapping copies and possible memory corruption or unexpected behavior at runtime. Red Hat subsequently shipped fixes for these Go flaws across multiple RHEL 8, 9, and 10 channels and dependent packages including **golang**, **rhc**, **ipp-usb**, **gvisor-tap-vsock**, and **Cryostat 4**, often alongside other Go vulnerabilities in `crypto/x509` and `internal/syscall/unix`. Advisories rated the updates **Important**, with `CVE-2026-32283` scored **CVSS 7.5** by Red Hat, and updated package builds were released for major architectures including `x86_64`, `aarch64`, `ppc64le`, and `s390x` across standard, EUS, AUS, SAP, and Extended Life Cycle offerings.
Aug 20, 2026
OpenSSH released security updates to address two vulnerabilities tracked as **CVE-2025-26465** and **CVE-2025-26466**, with downstream advisories warning that affected deployments could face both server impersonation and service disruption. According to vendor and researcher disclosures, **CVE-2025-26465** can enable a man-in-the-middle attack when `VerifyHostKeyDNS` is enabled, allowing an attacker to bypass host verification, present a crafted key, impersonate a trusted SSH server, and potentially intercept sessions, access sensitive data, or execute commands. The second issue, **CVE-2025-26466**, is a pre-authentication denial-of-service flaw caused by unbounded memory allocation triggered through `SSH2_MSG_PING` messages, which can exhaust memory and disrupt SSH availability. Guidance from OpenSSH and national CSIRT reporting urges organizations to upgrade to **OpenSSH 9.9p2 or later**, disable `VerifyHostKeyDNS` unless it is strictly required, and harden exposed services with connection controls such as `LoginGraceTime`, `MaxStartups`, and `PerSourcePenalties` to reduce exploitation risk.
Jul 24, 2026