Go 関連製品全体の CVE とセキュリティ脆弱性情報を集約し、CVSS、EPSS、公開日、脆弱性情報データを掲載しています。
一般的な弱点パターンには パス処理の欠陥、vendor risk cross-site scripting、vendor risk memory corruption, and vendor risk input validation があり、vendor surface production workloads の利用場面で ファイル上書き、vendor impact session compromise, and vendor impact unexpected behavior などのリスクが生じる可能性があります。
掲載データは公開脆弱性情報とセキュリティ公告に基づき、過去の暴露面と修補優先度の評価に利用できます。
| CVE | 概要 | ソース | CVSS 最大値 | EPSS（%） | 公開 | 更新 |
|---|---|---|---|---|---|---|
| CVE-2026-42506 | Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree. This can be leveraged to execute XSS attacks in applications that attempt to sanitize input HTML before rendering. | [email protected] | 6.1 | 0.03% | 2026-05-22 | 2026-05-29 |
| CVE-2026-42502 | Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree. This can be leveraged to execute XSS attacks in applications that attempt to sanitize input HTML before rendering. | [email protected] | 6.1 | 0.03% | 2026-05-22 | 2026-05-29 |
| CVE-2026-39821 | The ToASCII and ToUnicode functions incorrectly accept Punycode-encoded labels that decode to an ASCII-only label. For example, ToUnicode("xn--example-.com") incorrectly returns the name "example.com" rather than an error. This behavior can lead to privilege escalation in programs using the idna package. For example, a program which performs privilege checks on the ASCII hostname may reject "example.com" but permit "xn--example-.com". If that program subsequently converts the ASCII hostname to U | [email protected] | 9.6 | 0.05% | 2026-05-22 | 2026-05-29 |
| CVE-2026-27136 | Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree. This can be leveraged to execute XSS attacks in applications that attempt to sanitize input HTML before rendering. | [email protected] | 6.1 | 0.03% | 2026-05-22 | 2026-05-29 |
| CVE-2026-25681 | Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree. This can be leveraged to execute XSS attacks in applications that attempt to sanitize input HTML before rendering. | [email protected] | 6.1 | 0.03% | 2026-05-22 | 2026-05-29 |
| CVE-2026-25680 | Parsing arbitrary HTML can consume excessive CPU time, possibly leading to denial of service. | [email protected] | 6.5 | 0.06% | 2026-05-22 | 2026-05-29 |
| 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-2026-42501 | A malicious module proxy can exploit a flaw in the go command's validation of module checksums to bypass checksum database validation. This vulnerability affects any user using an untrusted module proxy (GOMODPROXY) or checksum database (GOSUMDB). A malicious module proxy can serve altered versions of the Go toolchain. When selecting a different version of the Go toolchain than the currently installed toolchain (due to the GOTOOLCHAIN environment variable, or a go.work or go.mod with a toolchain | [email protected] | 7.5 | 0.01% | 2026-05-07 | 2026-05-13 |