Is CVE-2026-46597 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-46597 being exploited in the wild.

How severe is CVE-2026-46597?

High severity, with a CVSS score of 7.5, published 22 May 2026.

Which products and versions are affected?

golang.org/x/crypto (Go) SEMVER:introduced=0,fixed=0.52.0; golang.org/x/crypto/ssh (Go) < 0.52.0.

Is there a fix for CVE-2026-46597?

Yes. golang.org/x/crypto (Go): upgrade to 0.52.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-46597 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-46597?

Check whether you run golang.org/x/crypto (Go) or golang.org/x/crypto/ssh (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-46597: Go x/crypto/ssh denial of service in AES-GCM decoder

Q: Is there a fix for CVE-2026-46597?

Yes. golang.org/x/crypto (Go): upgrade to 0.52.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-46597 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-46597?

Check whether you run golang.org/x/crypto (Go) or golang.org/x/crypto/ssh (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-46597 · Severity: high · CVSS 7.5 · Published 2026-05-22

A vulnerability in the Go SSH library could allow a remote attacker to crash a server by sending specially crafted network packets. This library is commonly used to build secure communication tools and remote access services. An exploit would result in a denial-of-service, making the affected service unavailable to legitimate users.

Technologies: golang.org/x/crypto (Go), golang.org/x/crypto/ssh (Go). Vendors: Go.

Quick answers

Is CVE-2026-46597 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-46597 being exploited in the wild.
How severe is CVE-2026-46597?: High severity, with a CVSS score of 7.5, published 22 May 2026.
Which products and versions are affected?: golang.org/x/crypto (Go) SEMVER:introduced=0,fixed=0.52.0; golang.org/x/crypto/ssh (Go) < 0.52.0.
Is there a fix for CVE-2026-46597?: Yes. golang.org/x/crypto (Go): upgrade to 0.52.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-46597 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-46597?: Check whether you run golang.org/x/crypto (Go) or golang.org/x/crypto/ssh (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

golang.org/x/crypto (Go): upgrade to 0.52.0 or later
```
go get golang.org/x/crypto@v0.52.0
```

Technical details

A vulnerability exists in the golang.org/x/crypto/ssh package due to an incorrectly placed type cast from bytes to int within the AES-GCM packet decoder. This flaw leads to an integer underflow during byte arithmetic, resulting in a runtime panic. A remote, unauthenticated attacker can exploit this by sending a well-crafted SSH packet to a server or client using the affected library. The issue impacts several functions including NewServerConn, NewClientConn, and Dial. The vulnerability is addressed in version 0.52.0 of the package.

Affected products

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

Identifiers

CVE-2026-46597
GHSA-q4h4-gmj2-qvw2
GO-2026-5013

Timeline

2026-05-21: disclosed: Issue reported to Go maintainers
2026-05-22: advisory: NVD and Go Vulnerability Database entries published
2026-06-25: patched: GitHub Advisory published for version 0.52.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.