CyberSecBulletin
CVE-2026-46595NVD status: Modified

golang.org/x/crypto/ssh: Incorrect Authorization

CVE-2026-46595 is a high-severity incorrect authorization vulnerability in golang.org/x/crypto/ssh from Golang.org/x/crypto, with a CVSS 3.1 base score of 7.1 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.56% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update golang.org/x/crypto/ssh to 0.52.0 or a later version.
  2. Update Crypto to 0.52.0 or a later version.
  3. Read the advisory on pkg.go.dev for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
Golang.org/x/cryptogolang.org/x/crypto/sshbefore 0.52.00.52.0
Red HatCryostat 4 on RHEL 9Not specified in the recordNot stated
Red HatRHEM 1.0 for RHEL 9Not specified in the recordNot stated
Red HatRHEM 1.1 for RHEL 10Not specified in the recordNot stated
Red HatRHEM 1.1 for RHEL 9Not specified in the recordNot stated
Red HatCert Manager support for Red Hat OpenShift release 1.19Not specified in the recordNot stated
Red HatCluster Observability Operator 1.5.0Not specified in the recordNot stated
Red HatDevWorkspace Operator 0.42Not specified in the recordNot stated
Red HatLogging Subsystem for Red Hat OpenShift 6.6Not specified in the recordNot stated
Red Hatmulticluster engine for Kubernetes 2.8Not specified in the recordNot stated
Red HatOpenShift API for Data Protection 1.3Not specified in the recordNot stated
Red HatOpenShift API for Data Protection 1.4Not specified in the recordNot stated
Red HatOpenShift API for Data Protection 1.5Not specified in the recordNot stated
Red HatOpenShift API for Data Protection 1.6Not specified in the recordNot stated
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.13Not specified in the recordNot stated
Red HatRed Hat Advanced Cluster Security 4.9Not specified in the recordNot stated
Red HatRed Hat Advanced Cluster Security for Kubernetes 4.10Not specified in the recordNot stated
Red HatRed Hat Advanced Cluster Security for Kubernetes 4.11Not specified in the recordNot stated
Red HatRed Hat Edge Manager 1.0Not specified in the recordNot stated
Red HatRed Hat Edge Manager 1.1Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux AI 3.4Not specified in the recordNot stated
Red HatRed Hat Hardened ImagesNot specified in the recordNot stated
Red HatRed Hat OpenShift AI 3.3Not specified in the recordNot stated
Red HatRed Hat OpenShift AI 3.4Not specified in the recordNot stated
Red HatRed Hat OpenShift Builds 1.7.3Not specified in the recordNot stated

Version data comes from the organisation that assigned the CVE; 32 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
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
LowPerformance or availability is reduced.

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L. Scored by CNA.

Scoring systemScoreSeverityScored by
CVSS 3.110.0CriticalCISA (ADP)
CVSS 3.17.1HighCNA

Official description

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Incorrect Authorization

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

How developers prevent this class of flaw

  • Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.

More Incorrect Authorization vulnerabilities (CWE-863)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in golang.org/x/crypto/ssh

All golang.org/x/crypto/ssh vulnerabilities

Recent Incorrect Authorization vulnerabilities

Spotted an error? Tell us.