golang.org/x/crypto/ssh: Improper Certificate Validation
CVE-2026-39828 is a high-severity improper certificate validation vulnerability in golang.org/x/crypto/ssh from Golang.org/x/crypto, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 0.52.0 as the first without the flaw, so updating golang.org/x/crypto/ssh to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.37% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update golang.org/x/crypto/ssh to 0.52.0 or a later version.
- Read the advisory on pkg.go.dev for workarounds and exact fixed builds.
Affected products and versions
Version data comes from the organisation that assigned the CVE; 35 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 6.3 | Medium | CISA (ADP) |
| CVSS 3.1 | 8.8 | High | CNA |
Official description
When an SSH server authentication callback returned PartialSuccessError with non-nil Permissions, those permissions were silently discarded, potentially dropping certificate restrictions such as force-command after a second factor succeeded. Returning non-nil Permissions with PartialSuccessError now results in a connection error.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Certificate Validation
The product does not validate, or incorrectly validates, a certificate.
How developers prevent this class of flaw
- Certificates should be carefully managed and checked to assure that data are encrypted with the intended owner's public key.
- If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname.
More Improper Certificate Validation vulnerabilities (CWE-295)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other references
- go.dev/cl/781621Issue Tracking
- go.dev/issue/79562Issue Tracking
- groups.google.com/g/golang-announce/c/a082jnz-LvIMailing List
- access.redhat.com/errata/RHSA-2026:26546
- access.redhat.com/errata/RHSA-2026:26547
- access.redhat.com/errata/RHSA-2026:36105
- access.redhat.com/errata/RHSA-2026:36167
- access.redhat.com/errata/RHSA-2026:36207
- access.redhat.com/errata/RHSA-2026:36319
- access.redhat.com/errata/RHSA-2026:36625
- access.redhat.com/errata/RHSA-2026:36648
- access.redhat.com/errata/RHSA-2026:36651
- access.redhat.com/errata/RHSA-2026:36796
- access.redhat.com/errata/RHSA-2026:36797
- access.redhat.com/errata/RHSA-2026:36808
Other vulnerabilities in golang.org/x/crypto/ssh
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.1 High severity
- 7.5 High severity
- 9.1 Critical severity
Recent Improper Certificate Validation vulnerabilities
- 8.8 High severity
- 7.4 High severity
- 8.7 High severity
- 7.5 High severity
- 8.2 High severity
- 7.4 High severity
Spotted an error? Tell us.