CVE-2026-39829: Invoking pathological RSA/DSA parameters may cause DoS in golang.org/x/crypto/ssh
The RSA and DSA public key parsers did not enforce size limits on key parameters. A crafted public key with an excessively large modulus or DSA parameter could cause several minutes of CPU consumption during signature verification. This could be triggered by unauthenticated clients during public key authentication. RSA moduli are now limited to 8192 bits, and DSA parameters are validated per FIPS 186-2.
Security readout for executives and security teams
Plain-English summary
A flaw in the Go SSH library lets an unauthenticated attacker send an oversized RSA or DSA public key that ties up server CPU for minutes during login. Repeated attempts can starve the service and disrupt SSH-dependent workflows. It is a denial-of-service issue, not data theft, but any Go-based SSH server or tool is potentially exposed until upstream fixes are applied.
Executive priority
Treat as a standard high-severity availability patch cycle. It will not leak data, but a single unauthenticated attacker can degrade SSH-dependent operations such as deployments, admin access, and Git workflows. Schedule patching in the next planned maintenance window and accelerate for any internet-facing Go SSH endpoints.
Technical view
The RSA and DSA public key parsers in golang.org/x/crypto/ssh did not cap key parameter sizes. A crafted key with a huge modulus or DSA parameters caused expensive signature verification during public key authentication, triggered pre-authentication. The upstream fix caps RSA moduli at 8192 bits and validates DSA parameters per FIPS 186-2. CVSS 3.1 base is 7.5 (AV:N/AC:L/PR:N/UI:N/A:H). CWE-1176 and CWE-1284 are cited.
Likely exposure
Any service embedding golang.org/x/crypto/ssh as a server that accepts public key authentication from untrusted networks is exposed. That includes Go-based bastions, Git hosting daemons, CI runners, and container tooling. Red Hat has shipped multiple RHSA advisories, indicating meaningful downstream reach across Kubernetes and OpenShift components. KEV does not list this CVE.
Exploitation context
No active exploitation is cited in the sources and the CVE is not in CISA KEV. The precondition is network reach to an SSH endpoint that will attempt key verification; no credentials or user interaction are required. Impact is availability only. Public references describe the flaw at a design level, not weaponized proof-of-concept code.
Researcher notes
Root cause is missing input validation on asymmetric key parameters before verification, matching CWE-1284. Fix caps RSA moduli at 8192 bits and enforces FIPS 186-2 DSA parameter checks. Pre-auth reachability makes this attractive for opportunistic DoS against bastions. Watch for downstream consumers such as Kubernetes, Terraform providers, and CI agents that vendor x/crypto and lag upstream updates.
Mitigation direction
Upgrade golang.org/x/crypto to the fixed release referenced by GO-2026-5018 and rebuild affected services.
Apply the relevant Red Hat RHSA errata to OpenShift, RHEL, and container images that ship affected Go binaries.
Where patching is delayed, restrict SSH exposure to trusted networks or place a rate-limiting proxy in front.
Inventory internal Go-based SSH servers and tools that vendor x/crypto/ssh and prioritize by internet exposure.
Confirm connection and authentication timeouts are enforced so slow verifications drop rather than accumulate.
Validation and detection
Run govulncheck against built binaries to confirm GO-2026-5018 no longer resolves against your modules.
Inspect go.mod and go.sum for golang.org/x/crypto versions below the fixed release across all services.
Cross-check installed RPMs against RHSA-2026:36796, 36199, 37072, and related errata for affected hosts.
Monitor SSH server CPU and authentication latency for spikes correlated with unauthenticated key attempts.
After patching, verify SSH daemons reject oversized RSA moduli and non-conforming DSA parameters in test.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-1176: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.