LiveActive security incident?Get immediate response
CVE Record

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.

CriticalCVSS 10Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

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.
Prepared
Confidence
medium
Sources
12

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.

Open ATT&CK lookup
cwe · medium confidence lookup

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.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-46595 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
10 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

2CVSS vectors
5Timeline events
2ADP providers
29Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

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.

ScoreVersionSeverityVectorExploitImpactSource
10CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L3.96CISA-ADP
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L1.65.5redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

10Critical
CVSS 3.1 vector shape for CVE-2026-46595Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
redhat-SADPgolang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Authorization bypass due to skipped source-address validation
other:Red Hat severity ratingcvssV3_1
  • 2026-05-22T04:01:52.215Z: Reported to Red Hat.
  • 2026-05-22T02:31:27.894Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
golang.org/x/cryptogolang.org/x/crypto/sshgolang.org/x/crypto/ssh, 0unaffected
Weakness

CWE details

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.

CWE-863 · source CWE mapping

Incorrect Authorization

Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.