golang.org/x/crypto/ssh

CVE-2026-39829

CVE-2026-39829 is a high-severity security vulnerability in golang.org/x/crypto/ssh (go), affecting versions < 0.52.0. It is fixed in 0.52.0.

Key facts
CVSS score
7.5
High
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
golang.org/x/crypto/ssh
Fixed in
0.52.0
Disclosed
2026

Summary

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.

Impact

Severity and exposure

CVE-2026-39829 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (0.52.0). Upgrading removes the vulnerable code path.

Affected versions

go

  • golang.org/x/crypto/ssh (< 0.52.0)

Security releases

  • golang.org/x/crypto/ssh → 0.52.0 (go)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-39829 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-39829 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2026-39829 in your environment

Remediation advice

Upgrade golang.org/x/crypto/ssh to 0.52.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-39829

What is CVE-2026-39829?

CVE-2026-39829 is a high-severity security vulnerability in golang.org/x/crypto/ssh (go), affecting versions < 0.52.0. It is fixed in 0.52.0.

How severe is CVE-2026-39829?

CVE-2026-39829 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of golang.org/x/crypto/ssh are affected by CVE-2026-39829?

golang.org/x/crypto/ssh (go) versions < 0.52.0 is affected.

Is there a fix for CVE-2026-39829?

Yes. CVE-2026-39829 is fixed in 0.52.0. Upgrade to this version or later.

Is CVE-2026-39829 exploitable, and should I be worried?

Whether CVE-2026-39829 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-39829 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-39829?

Upgrade golang.org/x/crypto/ssh to 0.52.0 or later.

Stop the waste.
Protect your environment with Kodem.