CVE-2026-39835
Analyzed Analyzed - Analysis Complete
SSH Server Panic via Nil CertChecker Callbacks

Publication date: 2026-05-22

Last updated on: 2026-05-28

Assigner: Go Project

Description
SSH servers which use CertChecker as a public key callback without setting IsUserAuthority or IsHostAuthority could be caused to panic by a client presenting a certificate. CertChecker now returns an error instead of panicking when these callbacks are nil.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-22
Last Modified
2026-05-28
Generated
2026-06-11
AI Q&A
2026-05-22
EPSS Evaluated
2026-06-10
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
golang crypto to 0.52.0 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-295 The product does not validate, or incorrectly validates, a certificate.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Compliance Impact

The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.

Executive Summary

This vulnerability affects SSH servers that use the CertChecker function as a public key callback. If the server does not set the IsUserAuthority or IsHostAuthority callbacks, a client presenting a certificate can cause the server to panic.

The issue arises because CertChecker previously would panic when these callbacks were nil. The fix changes CertChecker to return an error instead of panicking in such cases.

Impact Analysis

This vulnerability can cause an SSH server to panic and potentially crash when a client presents a certificate and the server's CertChecker callbacks are not properly set.

Such a panic could lead to denial of service, disrupting SSH access and potentially impacting availability of services relying on SSH connections.

Detection Guidance

This vulnerability occurs when an SSH server uses the CertChecker function as a public key callback without setting the IsUserAuthority or IsHostAuthority fields. Detection involves verifying the SSH server configuration and code to check if CertChecker is used without these fields set.

Since the vulnerability causes the server to panic when a client presents a certificate, monitoring SSH server logs for unexpected panics or crashes during certificate authentication attempts can help detect the issue.

There are no specific commands provided in the available resources to detect this vulnerability on a network or system.

Mitigation Strategies

To mitigate this vulnerability, ensure that when using the CertChecker function as a public key callback in your SSH server, the IsUserAuthority and IsHostAuthority fields are properly set.

Alternatively, update the golang.org/x/crypto/ssh package to version 0.52.0 or later, where CertChecker has been fixed to return an error instead of panicking when these callbacks are nil.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-39835. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart