What is the CVSS score of CVE-2026-46597?

CVE-2026-46597 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. EPSS exploitation probability: 0.0%.

Is there a public PoC exploit available for CVE-2026-46597?

Yes, a public proof-of-concept exploit is available for CVE-2026-46597. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-46597?

Within 24 hours: Inventory all internal Go applications and third-party services using golang.org/x/crypto/ssh; prioritize SSH servers exposed to untrusted networks. Within 7 days: Upgrade golang.org/x/crypto to version 0.52.0 or later and redeploy affected services. Within 30 days: Validate patch deployment across all systems and monitor for SSH connection anomalies or unexpected restart events.

golang.org/x/crypto/ssh CVE-2026-46597

Q: Which versions of golang.org/x/crypto/ssh are affected by CVE-2026-46597?

Go applications using the golang.org/x/crypto/ssh library (versions prior to 0.52.0) are vulnerable to denial-of-service attacks from remote, unauthenticated adversaries.. A patch is available.

EUVD-2026-31388 HIGH

Incorrect Type Conversion or Cast (CWE-704)

2026-05-22 Go

GHSA-q4h4-gmj2-qvw2

Information Disclosure Red Hat Golang Org X Crypto Ssh Golang Org X Crypto

7.5

CVSS 3.1 · Vendor: Go

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Identify reachable Go SSH server
Delivery

Open TCP connection to SSH port
Exploit

Negotiate AES-GCM during key exchange
Execution

Send crafted AES-GCM packet
Persist

Trigger bytes-to-int cast panic
Impact

SSH server process crashes

Vulnerability Assessment

Weakness	CWE CWE-704 ASVS 5.0 V15 - Secure Coding and Architecture Correct type conversion
Exploitation Conditions	Exploitation requires network reachability to a Go application that runs an SSH server using golang.org/x/crypto/ssh at a version below 0.52.0, and the SSH session must negotiate AES-GCM as the transport cipher (the default for most modern Go SSH servers). No authentication is required (PR:N) - the panic is triggered in the packet decoder before any user authentication completes, so an attacker only needs to complete the unauthenticated SSH transport-layer key exchange. Limiting factors: the bug only affects SSH server-side code paths (clients are not the target per the description), it does not affect deployments that have disabled AES-GCM ciphers, and only Go applications that actually expose an SSH listener (not those using the library purely as a client) are at risk.
Impact	The CVSS 7.5 score (AV:N/AC:L/PR:N/UI:N/C:N/I:N/A:H) reflects unauthenticated network-reachable denial of service against availability only, with no confidentiality or integrity impact - consistent with a panic-based crash rather than memory corruption or info leak. CISA's SSVC framework rates Exploitation as 'none' (no observed exploitation) but Automatable as 'yes' with partial technical impact, meaning crafting a reusable crash payload is straightforward once reverse-engineered. EPSS is very low (0.02%, 5th percentile) and no KEV listing exists, so this is a real but not urgent priority - patch on normal cycles unless the SSH endpoint is exposed to untrusted networks. Note: the 'Information Disclosure' tag in the input conflicts with the CVSS vector (C:N) and the description (panic/DoS); the CVSS vector and description should be treated as authoritative, and the tag appears mislabeled.
Exploit ScenarioDerived	An attacker who can reach a vulnerable Go-based SSH server on TCP/22 (or whatever port it listens on) opens a TCP connection, completes enough of the SSH transport handshake to negotiate AES-GCM, and then sends a single crafted encrypted packet that triggers the bad cast. The server process panics and terminates, denying service to all legitimate users; an attacker can script this to crash the service repeatedly upon restart. No public exploit identified at time of analysis, but the SSVC 'Automatable: yes' rating indicates a working crash payload would be trivial to weaponize once the patch is diffed.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 28, 2026

Denial of service in the Go golang.org/x/crypto/ssh package (versions prior to 0.52.0) allows remote unauthenticated attackers to crash SSH server processes by sending crafted AES-GCM encrypted packets. An incorrectly placed bytes-to-int cast in the AES-GCM packet decoder triggers a server-side panic when processing well-crafted inputs. No public exploit identified at time of analysis, and EPSS exploitation probability is very low at 0.02%.

RemediationAI

Upgrade the golang.org/x/crypto dependency to version 0.52.0 or later (Vendor-released patch: 0.52.0), then rebuild and redeploy any Go binary that embeds an SSH server - run 'go get golang.org/x/crypto@v0.52.0' followed by 'go mod tidy' and verify with 'govulncheck ./...' against GO-2026-5013. The fix landed in Go change https://go.dev/cl/781620 and was announced at https://groups.google.com/g/golang-announce/c/a082jnz-LvI. If immediate patching is not possible, compensating controls include restricting SSH server exposure to trusted source IPs via firewall/security-group ACLs and disabling AES-GCM ciphers in the server's negotiated cipher list (falling back to ChaCha20-Poly1305 or AES-CTR) - the trade-off is reduced interoperability with clients that only support GCM and a small performance penalty for ChaCha20-Poly1305 on platforms without AES-NI.

Affected VersionsENISA

golang.org/x/crypto/ssh 0 <0.52.0

Affected Packages

go golang.org/x/crypto fix: 0.52.0

go golang.org/x/crypto/ssh fix: 0.52.0

euvd golang_org_x_crypto_ssh fix: 0.52.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 3 packages in go, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability resides in golang.org/x/crypto/ssh, the official Go SSH protocol implementation widely embedded in Go-based servers, bastions, CI/CD agents, and tooling (per CPE cpe:2.3:a:golang.org/x/crypto:golang.org/x/crypto/ssh). The root cause is classified as CWE-704 (Incorrect Type Conversion or Cast): an incorrectly placed cast from bytes to int within the AES-GCM packet decoder. When the decoder processes a malformed but well-formed-enough encrypted packet, the bad cast leads to a runtime panic, terminating the SSH server goroutine or process. AES-GCM is one of the default authenticated encryption modes negotiated during SSH transport setup, so the decoder is reached early in any SSH session.

Know when Golang Org X Crypto Ssh gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

Vendor (Go) PRIMARY 7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

SUSE HIGH

Red Hat 7.5 HIGH

Primary rating from Vendor (Go).

CVSS VectorVendor: Go

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

CVSS changed

May 28, 2026 - 15:07 NVD

7.5 (None) 7.5 (HIGH)

Patch available

May 22, 2026 - 04:31 EUVD

CVE Published

May 22, 2026 - 02:31 nvd

UNKNOWN (no severity yet)

DescriptionCVE.org

An incorrectly placed cast from bytes to int allowed for server-side panic in the AES-GCM packet decoder for well-crafted inputs.

Executive ViewAI

Why It Matters

Go applications using the golang.org/x/crypto/ssh library (versions prior to 0.52.0) are vulnerable to denial-of-service attacks from remote, unauthenticated adversaries. A flaw in AES-GCM packet decoding allows attackers to crash SSH server processes with crafted encrypted packets, directly impacting service availability for any organization relying on SSH for administrative access or infrastructure management.

Business Impact: High

Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score

0.0%

Top 95% exploitable

Threat Intel

1 sources

Exploit

POC

Public exploit code exists

Social Media

Sightings

Data Quality

8 sources

Confidence: High

EUVD

NVD

CVE.org

EPSS

Vulnrichment GHSA MSRC Vendor CIRCL

GitHub

VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC Yes

EPSS 0.0%

Patch available Yes

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision

Scheduled

Exploitation

None

System Exposure· derived

Open

Automatable

Yes

Human Impact

High

Technical Impact

Partial

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +38

PoC: +20

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.