This page lists publicly disclosed CVE vulnerabilities affecting golang crypto (linked via NVD CPE). Each row includes severity scores, summaries, and publication dates to help identify and analyze security issues.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2026-46598 | For certain crafted inputs, a 'ed25519.PrivateKey' was created by casting malformed wire bytes, leading to a panic when used. | [email protected] | 5.3 | 0.05% | 2026-05-22 | 2026-05-28 |
| CVE-2026-46597 | An incorrectly placed cast from bytes to int allowed for server-side panic in the AES-GCM packet decoder for well-crafted inputs. | [email protected] | 7.5 | 0.06% | 2026-05-22 | 2026-05-28 |
| CVE-2026-46595 | 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. | [email protected] | 10.0 | 0.05% | 2026-05-22 | 2026-05-28 |
| CVE-2026-42508 | Previously, a revoked 'SignatureKey' belonging to a CA was not correctly checked for revocation. Now, both the 'key' and 'key.SignatureKey' are checked for @revoked. | [email protected] | 9.1 | 0.02% | 2026-05-22 | 2026-05-28 |
| CVE-2026-39835 | SSH servers which use CertChecker as a public key callback without setting IsUserAuthority or IsHostAuthority could be caused to panic by a client presenting a certificate. CertChecker now returns an error instead of panicking when these callbacks are nil. | [email protected] | 5.3 | 0.01% | 2026-05-22 | 2026-05-28 |
| CVE-2026-39834 | When writing data larger than 4GB in a single Write call on an SSH channel, an integer overflow in the internal payload size calculation caused the write loop to spin indefinitely, sending empty packets without making progress. The size comparison now uses int64 to prevent truncation. | [email protected] | 9.1 | 0.06% | 2026-05-22 | 2026-05-28 |
| CVE-2026-39833 | The in-memory keyring returned by NewKeyring() silently accepted keys with the ConfirmBeforeUse constraint but never enforced it. The key would sign without any confirmation prompt, with no indication to the caller that the constraint was not in effect. NewKeyring() now returns an error when unsupported constraints are requested. | [email protected] | 9.1 | 0.02% | 2026-05-22 | 2026-05-28 |
| CVE-2026-39832 | When adding a key to a remote agent constraint extensions such as [email protected] were not serialized in the request. Destination restrictions were silently stripped when forwarding keys, allowing unrestricted use of the key on the remote host. The client now serializes all constraint extensions. Additionally, the in-memory keyring returned by NewKeyring() now rejects keys with unsupported constraint extensions instead of silently ignoring them. | [email protected] | 9.1 | 0.07% | 2026-05-22 | 2026-05-28 |
| CVE-2026-39831 | The Verify() method for FIDO/U2F security key types ([email protected], [email protected]) did not check the User Presence flag. Signatures generated without physical touch were accepted, allowing unattended use of a hardware security key. To restore the previous behavior, return a "no-touch-required" extension in Permissions.Extensions from PublicKeyCallback. | [email protected] | 9.1 | 0.01% | 2026-05-22 | 2026-06-02 |
| CVE-2026-39830 | A malicious SSH peer could send unsolicited global request responses to fill an internal buffer, blocking the connection's read loop. The blocked goroutine could not be released by calling Close(), resulting in a resource leak per connection. Unsolicited global responses are now discarded. | [email protected] | 9.1 | 0.06% | 2026-05-22 | 2026-06-02 |
| CVE-2026-39829 | The RSA and DSA public key parsers did not enforce size limits on key parameters. A crafted public key with an excessively large modulus or DSA parameter could cause several minutes of CPU consumption during signature verification. This could be triggered by unauthenticated clients during public key authentication. RSA moduli are now limited to 8192 bits, and DSA parameters are validated per FIPS 186-2. | [email protected] | 7.5 | 0.03% | 2026-05-22 | 2026-06-02 |
| CVE-2026-39828 | When an SSH server authentication callback returned PartialSuccessError with non-nil Permissions, those permissions were silently discarded, potentially dropping certificate restrictions such as force-command after a second factor succeeded. Returning non-nil Permissions with PartialSuccessError now results in a connection error. | [email protected] | 6.3 | 0.01% | 2026-05-22 | 2026-06-02 |
| CVE-2026-39827 | An authenticated SSH client that repeatedly opened channels which were rejected by the server caused unbounded memory growth, eventually crashing the server process and affecting all connected users. Rejected channels are now properly removed from the connection's internal state and released for garbage collection. | [email protected] | 6.5 | 0.02% | 2026-05-22 | 2026-05-26 |
| CVE-2025-58181 | SSH servers parsing GSSAPI authentication requests do not validate the number of mechanisms specified in the request, allowing an attacker to cause unbounded memory consumption. | [email protected] | 5.3 | 0.04% | 2025-11-19 | 2025-12-11 |
| CVE-2025-47914 | SSH Agent servers do not validate the size of messages when processing new identity requests, which may cause the program to panic if the message is malformed due to an out of bounds read. | [email protected] | 5.3 | 0.02% | 2025-11-19 | 2025-12-11 |
| CVE-2023-48795 | The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the ha | [email protected] | 5.9 | 51.66% | 2023-12-18 | 2026-05-12 |
| CVE-2019-11841 | A message-forgery issue was discovered in crypto/openpgp/clearsign/clearsign.go in supplementary Go cryptography libraries 2019-03-25. According to the OpenPGP Message Format specification in RFC 4880 chapter 7, a cleartext signed message can contain one or more optional "Hash" Armor Headers. The "Hash" Armor Header specifies the message digest algorithm(s) used for the signature. However, the Go clearsign package ignores the value of this header, which allows an attacker to spoof it. Consequent | [email protected] | 5.9 | 0.40% | 2019-05-22 | 2024-11-21 |
| CVE-2019-11840 | An issue was discovered in the supplementary Go cryptography library, golang.org/x/crypto, before v0.0.0-20190320223903-b7391e95e576. A flaw was found in the amd64 implementation of the golang.org/x/crypto/salsa20 and golang.org/x/crypto/salsa20/salsa packages. If more than 256 GiB of keystream is generated, or if the counter otherwise grows greater than 32 bits, the amd64 implementation will first generate incorrect output, and then cycle back to previously generated keystream. Repeated keystre | [email protected] | 5.9 | 2.14% | 2019-05-09 | 2026-05-18 |
| CVE-2017-3204 | The Go SSH library (x/crypto/ssh) by default does not verify host keys, facilitating man-in-the-middle attacks. Default behavior changed in commit e4e2799 to require explicitly registering a hostkey verification mechanism. | [email protected] | 8.1 | 0.53% | 2017-04-04 | 2026-05-13 |