CVE-2026-46597: Invoking byte arithmetic causes underflow and panic in golang.org/x/crypto/ssh

Published May 22, 2026
·
Updated

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

Other sources

Invoking byte arithmetic causes underflow and panic in golang.org/x/crypto/ssh

— Microsoft

Affected Software

36 affected componentsFixes available
golang/golang.org/x/crypto/ssh
Microsoft azl3 telegraf 1.31.0-19
Patch available
Microsoft azl3 gh 2.62.0-15
Patch available
Microsoft azl3 docker-buildx 0.14.0-11
Patch available
Microsoft azl3 cf-cli 8.7.11-5
Patch available
Microsoft azl3 docker-compose 2.27.0-9
Patch available
Microsoft azl3 kubevirt 1.7.1-2
Patch available
Microsoft azl3 packer 1.9.5-13
Patch available
Microsoft azl3 cert-manager 1.12.15-6
Patch available
Microsoft azl3 moby-engine 25.0.3-17
Patch available
Microsoft azl3 kubernetes 1.30.10-23
Patch available
Microsoft azl3 kubernetes 1.30.10-25
Patch available
Microsoft azl3 moby-engine 25.0.3-18
Patch available
go/golang.org/x/crypto/ssh<0.52.0
0.52.0
Golang Crypto Go<0.52.0
IBM Concert Software<=1.0-3.0.0
All of the following
azurelinux/kubernetes<1.30.10-25
1.30.10-25
Microsoft Azure Linux=3.0
All of the following
azurelinux/packer<1.9.5-14
1.9.5-14
Microsoft Azure Linux=3.0
All of the following
azurelinux/moby-engine<25.0.3-18
25.0.3-18
Microsoft Azure Linux=3.0
All of the following
azurelinux/cert-manager<1.12.15-8
1.12.15-8
Microsoft Azure Linux=3.0
All of the following
azurelinux/gh<2.62.0-16
2.62.0-16
Microsoft Azure Linux=3.0
All of the following
azurelinux/telegraf<1.31.0-21
1.31.0-21
Microsoft Azure Linux=3.0
All of the following
azurelinux/cf-cli<8.7.11-6
8.7.11-6
Microsoft Azure Linux=3.0
All of the following
azurelinux/docker-compose<2.27.0-11
2.27.0-11
Microsoft Azure Linux=3.0
All of the following
azurelinux/kubevirt<1.7.1-5
1.7.1-5
Microsoft Azure Linux=3.0
All of the following
azurelinux/docker-buildx<0.14.0-13
0.14.0-13
Microsoft Azure Linux=3.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/golang.org/x/crypto/ssh to a version that resolves this vulnerability.

    Fixed in 0.52.0
  2. Upgrade

    Upgrade azurelinux/kubernetes to a version that resolves this vulnerability.

    Fixed in 1.30.10-25
  3. Upgrade

    Upgrade azurelinux/moby-engine to a version that resolves this vulnerability.

    Fixed in 25.0.3-18
  4. Upgrade

    Upgrade azurelinux/packer to a version that resolves this vulnerability.

    Fixed in 1.9.5-14
  5. Upgrade

    Upgrade azurelinux/cert-manager to a version that resolves this vulnerability.

    Fixed in 1.12.15-8
  6. Upgrade

    Upgrade azurelinux/gh to a version that resolves this vulnerability.

    Fixed in 2.62.0-16
  7. Upgrade

    Upgrade azurelinux/telegraf to a version that resolves this vulnerability.

    Fixed in 1.31.0-21
  8. Upgrade

    Upgrade azurelinux/cf-cli to a version that resolves this vulnerability.

    Fixed in 8.7.11-6
  9. Upgrade

    Upgrade azurelinux/docker-buildx to a version that resolves this vulnerability.

    Fixed in 0.14.0-13
  10. Upgrade

    Upgrade azurelinux/kubevirt to a version that resolves this vulnerability.

    Fixed in 1.7.1-5
  11. Upgrade

    Upgrade azurelinux/docker-compose to a version that resolves this vulnerability.

    Fixed in 2.27.0-11

Event History

May 22, 2026
CVE Published
via MITRE·02:31 AM
Data Sourced
via MITRE·02:31 AM
DescriptionWeakness
Data Sourced
via Red Hat·04:01 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·04:16 AM
DescriptionSeverityWeaknessAffected Software
May 27, 2026
Data Sourced
via Microsoft·08:13 AM
DescriptionSeverityWeaknessAffected Software
Jun 25, 2026
Advisory Published
via GitHub·10:14 PM
Data Sourced
via GitHub·10:14 PM
DescriptionSeverityWeaknessAffected Software
Oct 14, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2026-46597?

CVE-2026-46597 has a risk level of 40, indicating a moderate severity vulnerability.

2

How do I fix CVE-2026-46597?

To mitigate CVE-2026-46597, update to the latest version of golang.org/x/crypto/ssh that addresses this vulnerability.

3

What causes CVE-2026-46597?

CVE-2026-46597 is caused by an incorrectly placed cast from bytes to int in the AES-GCM packet decoder.

4

What impact does CVE-2026-46597 have on its users?

CVE-2026-46597 can lead to a server-side panic, which affects the stability and security of applications using the library.

5

Is CVE-2026-46597 exploitable?

Yes, well-crafted inputs can exploit CVE-2026-46597 to trigger an underflow and invoke a panic in the application.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203