CVE-2026-46595 Invoking VerifiedPublicKeyCallback permissions skip enforcement in golang.org/x/crypto/ssh

Critical 10.0 Published Updated

Attackers can bypass source-address validation in SSH servers if non-public-key callbacks are used, requiring specific server configurations.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-46595?

CVE-2026-46595 is a critical authentication bypass vulnerability in golang.org/x/crypto/ssh, published on 22 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

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.

Weakness: CWE-303, CWE-863

Which versions are affected by CVE-2026-46595?

3 open source packages ship an affected version, including golang.org/x/crypto. It affects 1 product.

PackageAffectedFixed in
golang.org/x/crypto GoAll versions0.52.0
golang.org/x/crypto GoAll versions0.52.0
golang.org/x/crypto GoAll versions0.52.0
Linux distribution packages (1)
distribution openSUSE:TumbleweedAll versions3.1.2-1.1

Products include Golang Crypto.

How do I fix CVE-2026-46595?

Upgrade golang.org/x/crypto to 0.52.0 or later.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2026-46595 being exploited?

There is no known exploitation of CVE-2026-46595 in the wild and no public exploit code.

Public exploit code: 1 proofs of concept on GitHub.

Sources

Also known as AZL-87179, AZL-87227, AZL-87326, BELL-CVE-2026-46595, CLEANSTART-2026-AM91695, CLEANSTART-2026-BD72670 and 1121 more.

Is CVE-2026-46595 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free