Authentication bypass via skipped source-address validation
Published Aug 28, 2026 · Updated Aug 28, 2026
Incorrect authorization in golang.org/x/crypto/ssh before 0.55.0 allows remote attackers to bypass source-address access controls. In connection.serverAuthenticate, permissions from four non-public-key callbacks bypass validation against the client's remote address. Exploitation requires a server to return a source-address restriction from an affected callback, after which an out-of-range client obtains the SSH access otherwise granted by that callback.
Summary
What happened
Incorrect authorization in golang.org/x/crypto/ssh before 0.55.0 allows remote attackers to bypass source-address access controls. In connection.serverAuthenticate, permissions from four non-public-key callbacks bypass validation against the client's remote address. Exploitation requires a server to return a source-address restriction from an affected callback, after which an out-of-range client obtains the SSH access otherwise granted by that callback.
The record
- CVE
- CVE-2026-56854
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- golang.org/x/crypto
- Product
- golang.org/x/crypto/ssh
- Classifications
- CWE-346, CWE-863, T1021.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.55.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo