CVE-2026-46595: Invoking VerifiedPublicKeyCallback permissions skip enforcement in golang.org/x/crypto/ssh
Previously, CVE-2024-45337 fixed an authorization bypass for misused ssh server configurations; if any other type of callback is passed other than public key, then the source-address validation would be skipped.
Security readout for executives and security teams
Plain-English summary
This is an authorization bypass in Go's x/crypto/ssh library. Certain SSH server configurations could skip source-address permission enforcement when callbacks other than the public-key callback are involved. The worst case is unauthorized network access to SSH functionality in affected Go-based services.
Executive priority
Treat as urgent for teams running Go-based SSH services or affected Red Hat-packaged products. The business priority is rapid inventory and patch confirmation, focused on internet-facing administrative or file-transfer paths.
Technical view
CVE-2026-46595 affects golang.org/x/crypto/ssh and relates to incomplete enforcement around VerifiedPublicKeyCallback permissions. The source bundle says non-public-key callback paths could skip source-address validation, extending the prior CVE-2024-45337 issue. CVSS is 10.0 with network attack vector and no required privileges or user interaction.
Likely exposure
Exposure is most likely in Go applications or vendor products embedding golang.org/x/crypto/ssh as an SSH server and relying on callback-enforced source-address restrictions. It should not be assumed to affect unrelated SSH servers without x/crypto/ssh usage.
Exploitation context
The provided bundle does not show CISA KEV listing or confirmed active exploitation. The risk is still serious because the CVSS vector indicates remote, unauthenticated reachability and high confidentiality and integrity impact when vulnerable configurations are present.
Researcher notes
Evidence supports an authorization bypass tied to callback handling and source-address validation. The source bundle does not provide exploit details, affected fixed-version ranges, or proof of exploitation, so validation should center on dependency presence, configuration pattern, and vendor advisory status.
Mitigation direction
Check Go advisory GO-2026-5023 for the fixed x/crypto version.
Apply relevant vendor updates, including listed Red Hat errata where applicable.
Inventory Go services and products embedding golang.org/x/crypto/ssh.
Review SSH server callback configurations that enforce source-address restrictions.
Prioritize externally reachable SSH services using this library.
Validation and detection
Identify dependencies on golang.org/x/crypto/ssh in Go module inventories.
Confirm deployed builds include the vendor-advised fixed library version.
Review whether SSH server code uses affected callback and permissions patterns.
Check vendor SBOMs or advisories for embedded x/crypto/ssh usage.
Verify applicable Red Hat advisories are installed on managed systems.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-303: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-303 · source CWE mapping
Incorrect Implementation of Authentication Algorithm
Incorrect Implementation of Authentication Algorithm represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.