dbcve.org
CryptoApplication · Golang

CVE-2026-46595

CRITICAL · 10.0 CVSS v3.1 Published 2026-05-22
Fix available
A fix is available. Upgrade to 0.52.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a security bypass vulnerability in an SSH server library where CVE-2024-45337 attempted to fix source-address validation but only applied it to public key authentication callbacks. If other authentication callback types (password, keyboard-interactive, etc.) are used, the source-address validation is completely skipped, allowing attackers to bypass IP-based access controls.

MitigationEnsure source-address validation is applied to ALL authentication callback types, not just public key. Review all callback handlers in the SSH server implementation and apply consistent IP validation logic.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CryptoApplication
Affected:< 0.52.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify golang.org/x/crypto version
    Check your go.mod file or run 'go list -m golang.org/x/crypto' to find the installed version of the crypto library
    Affected if version is earlier than 0.52.0
  2. Locate SSH server code using crypto/ssh
    Search for imports of golang.org/x/crypto/ssh and usage of ServerConfig with custom callback fields such as PasswordCallback, KeyboardInteractiveCallback, or Authentications
    Affected if the SSH server configuration defines any callback type other than or in addition to PublicKeyCallback
  3. Review IP-based access control implementation
    Inspect the source-address validation logic in your SSH server callback handlers to see if IP filtering is implemented
    Affected if IP-based restrictions are enforced only within PublicKeyCallback and not consistently applied to PasswordCallback, KeyboardInteractiveCallback, or other authentication methods
  4. Check for custom callback handlers
    Examine your SSH server implementation for HandleAuthRequestFunc or custom callback functions that handle authentication
    Affected if custom authentication callbacks are registered that do not perform source address validation before processing credentials

You are affected if golang.org/x/crypto version is below 0.52.0 AND your SSH server uses any authentication callback type other than public key authentication, since source address validation would be bypassed for those methods.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.52.0 or later
Fixed in 0.52.0
Interim mitigation

Ensure source-address validation is applied to ALL authentication callback types, not just public key. Review all callback handlers in the SSH server implementation and apply consistent IP validation logic.

Recommended fix High confidence

golang.org/x/crypto v0.52.0 or later

  1. Run `go get golang.org/x/crypto@latest` or specifically `go get golang.org/x/[email protected]` to upgrade to the fixed version
  2. Run `go mod tidy` to update go.mod and go.sum files
  3. Run your test suite to verify the upgrade does not break existing functionality
  4. Rebuild and redeploy your application

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Crypto Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46595 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46595 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data