CVE-2026-46595
Authorization Bypass in Go SSH Server via Callback Misuse
Publication date: 2026-05-22
Last updated on: 2026-05-22
Assigner: Go Project
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| golang | go | to v0.52.0 (exc) |
| golang | golang.org | to v0.52.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-46595 is an authorization bypass vulnerability in Go's SSH server implementation. It occurs because the permissions enforcement for the VerifiedPublicKeyCallback is skipped under certain misconfigured scenarios.
Specifically, if a callback other than the public key callback is passed to the SSH server, the source-address validation is bypassed, allowing unauthorized access. This issue is a continuation of a previously fixed problem (CVE-2024-45337) but affects other callback types that were not fully addressed.
How can this vulnerability impact me? :
This vulnerability can allow unauthorized users to bypass authorization checks in Go's SSH server implementations if the server is misconfigured to use certain callbacks other than the public key callback.
As a result, attackers could gain access to systems or services that rely on the affected SSH server for authentication, potentially leading to unauthorized data access or control over the affected system.
What immediate steps should I take to mitigate this vulnerability?
This vulnerability affects the golang.org/x/crypto/ssh package before version v0.52.0 and involves an authorization bypass due to skipped source-address validation when callbacks other than public key are used.
Immediate mitigation steps include upgrading the golang.org/x/crypto/ssh package to version v0.52.0 or later once the fix is released.
Until a fix is available, review and avoid using non-public key callbacks in SSH server configurations to prevent bypassing source-address validation.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify any direct impact of CVE-2026-46595 on compliance with common standards and regulations such as GDPR or HIPAA.