golang.org/x/crypto/ssh/knownhosts: Improper Certificate Validation
CVE-2026-42508 is a high-severity improper certificate validation vulnerability in golang.org/x/crypto/ssh/knownhosts from Golang.org/x/crypto, with a CVSS 3.1 base score of 7.4 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, 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/knownhosts to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 6.91% chance of exploitation within 30 days, which is in the top 5.81% of all scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update golang.org/x/crypto/ssh/knownhosts to 0.52.0 or a later version.
- Update Crypto to 0.52.0 or a later version.
- Read the advisory on pkg.go.dev for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
Version data comes from the organisation that assigned the CVE; 31 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
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- 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
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N. Scored by CNA.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.1 | Critical | CISA (ADP) |
| CVSS 3.1 | 7.4 | High | CNA |
Official description
Previously, a revoked 'SignatureKey' belonging to a CA was not correctly checked for revocation. Now, both the 'key' and 'key.SignatureKey' are checked for @revoked.
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: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other references
- go.dev/cl/781220Issue Tracking
- go.dev/issue/79568Issue Tracking
- groups.google.com/g/golang-announce/c/a082jnz-LvIMailing List
- access.redhat.com/errata/RHSA-2026:23262
- access.redhat.com/errata/RHSA-2026:23264
- access.redhat.com/errata/RHSA-2026:26546
- access.redhat.com/errata/RHSA-2026:26547
- access.redhat.com/errata/RHSA-2026:35833
- 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
- access.redhat.com/errata/RHSA-2026:37072
- access.redhat.com/errata/RHSA-2026:37123
Recent Improper Certificate Validation vulnerabilities
- 8.8 High severity
- 7.5 High severity
- 8.8 High severity
- 8.7 High severity
- 7.5 High severity
- 8.2 High severity
Spotted an error? Tell us.