GoLang
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in any GoLang product.
RSS Feeds for GoLang security vulnerabilities
Create a CVE RSS feed including security vulnerabilities found in GoLang products with stack.watch. Just hit watch, then grab your custom RSS feed url.
Products by GoLang Sorted by Most Security Vulnerabilities since 2018
By the Year
In 2026 there have been 17 vulnerabilities in GoLang with an average score of 7.0 out of ten. Last year, in 2025 GoLang had 9 security vulnerabilities published. That is, 8 more vulnerabilities have already been reported in 2026 as compared to last year. However, the average CVE base score of the vulnerabilities in 2026 is greater by 0.47.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 17 | 7.01 |
| 2025 | 9 | 6.54 |
| 2024 | 8 | 8.15 |
| 2023 | 40 | 7.43 |
| 2022 | 33 | 7.24 |
| 2021 | 18 | 7.14 |
| 2020 | 14 | 6.72 |
| 2019 | 7 | 6.88 |
| 2018 | 5 | 7.90 |
It may take a day or so for new GoLang vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent GoLang Security Vulnerabilities
| CVE | Date | Vulnerability | Products |
|---|---|---|---|
| CVE-2026-39820 | May 07, 2026 |
Go net/mail 1.25.x-1.26.3: ParseAddress/Date CPU/Memory ExhaustionWell-crafted inputs reaching ParseAddress, ParseAddressList, and ParseDate were able to trigger excessive CPU exhaustion and memory allocations. |
Go
|
| CVE-2026-42501 | May 07, 2026 |
GO cmd/go Validation Bypass for Module Checksum in 1.25.10/1.26.2A 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 line), the go command will download and execute a toolchain provided by the module proxy. A malicious module proxy can bypass checksum database validation for this downloaded toolchain. Since this vulnerability affects the security of toolchain downloads, setting GOTOOLCHAIN to a fixed version is not sufficient. You must upgrade your base Go toolchain. The go tool always validates the hash of a toolchain before executing it, so fixed versions will refuse to execute any cached, altered versions of the toolchain. The go tool trusts go.sum files to contain accurate hashes of the current module's dependencies. A malicious proxy exploiting this vulnerability to serve an altered module will have caused an incorrect hash to be recorded in the go.sum. Users who have configured a non-trusted GOPROXY can determine if they have been affected by running "rm go.sum ; go mod tidy ; go mod verify", which will revalidate all dependencies of the current module. The specific flaw in more detail: The go command consults the checksum database to validate downloaded modules, when a module is not listed in the go.sum file. It verifies that the module hash reported by the checksum database matches the hash of the downloaded module. If, however, the checksum database returns a successful response that contains no entry for the module, the go command incorrectly permitted validation to succeed. A module proxy may mirror or proxy the checksum database, in which case the go command will not connect to the checksum database directly. Checksums reported by the checksum database are cryptographically signed, so a malicious proxy cannot alter the reported checksum for a module. However, a proxy which returns an empty checksum response, or a checksum response for an unrelated module, could cause the go command to proceed as if a downloaded module has been validated. |
Go
|
| CVE-2026-39817 | May 07, 2026 |
Go Toolchain Pack Subcmd Arbitrary File Write (1.251.26.2)The "go tool pack" subcommand (usually used only by the compiler as an internal tool with known-good inputs) does not sanitize output filenames. Extracting a malicious archive file with the "pack" subcommand can write files to arbitrary locations on the filesystem. |
Go
|
| CVE-2026-39819 | May 07, 2026 |
Go toolchain cmd/go 1.25.10, 1.26.3: temp file overwriteThe "go bug" command writes to two files with predictable names in the system temporary directory (for example, "/tmp"). An attacker with access to the temporary directory can create a symlink in one of these names, causing "go bug" to overwrite the target of the symlink. |
Go
|
| CVE-2026-39826 | May 07, 2026 |
Go html/template <script> type attr escape flaw before 1.25.10 & <1.26.3If a trusted template author were to write a <script> tag containing an empty 'type' attribute or a 'type' attribute with an ASCII whitespace, the execution of the template would incorrectly escape any data passed into the <script> block. |
Go
|
| CVE-2026-33814 | May 07, 2026 |
Go HTTP/2 Infinity Loop from SETTINGS_MAX_FRAME_SIZE=0When processing HTTP/2 SETTINGS frames, transport will enter an infinite loop of writing CONTINUATION frames if it receives a SETTINGS_MAX_FRAME_SIZE with a value of 0. |
Go
|
| CVE-2026-32280 | Apr 08, 2026 |
Go crypto/x509 Intermediates DoS (<=1.26.2)During chain building, the amount of work that is done is not correctly limited when a large number of intermediate certificates are passed in VerifyOptions.Intermediates, which can lead to a denial of service. This affects both direct users of crypto/x509 and users of crypto/tls. |
Go
|
| CVE-2026-27140 | Apr 08, 2026 |
SWIG cgo filename execution in Go cmd/go <1.26.2SWIG file names containing 'cgo' and well-crafted payloads could lead to code smuggling and arbitrary code execution at build time due to trust layer bypass. |
Go
|
| CVE-2026-32281 | Apr 08, 2026 |
CVE-2026-32281: DoS via Policy Map Ineff in Go crypto/x509 <1.25.9, <1.26.2Validating certificate chains which use policies is unexpectedly inefficient when certificates in the chain contain a very large number of policy mappings, possibly causing denial of service. This only affects validation of otherwise trusted certificate chains, issued by a root CA in the VerifyOptions.Roots CertPool, or in the system certificate pool. |
Go
|
| CVE-2026-27143 | Apr 08, 2026 |
Go cmd/compile 1.25.9/1.26.2 Induction Variable Underflow VulnerabilityArithmetic over induction variables in loops were not correctly checked for underflow or overflow. As a result, the compiler would allow for invalid indexing to occur at runtime, potentially leading to memory corruption. |
Go
|
| CVE-2026-27144 | Apr 08, 2026 |
Memory Corruption in Go Compiler (cmd/compile) <1.25.9, 1.26.0-1.26.2The compiler is meant to unwrap pointers which are the operands of a memory move; a no-op interface conversion prevented the compiler from making the correct determination about non-overlapping moves, potentially leading to memory corruption at runtime. |
Go
|
| CVE-2026-27142 | Mar 06, 2026 |
Go html/template XSS via meta content URL unescape <1.25.8, 1.26.0Actions which insert URLs into the content attribute of HTML meta tags are not escaped. This can allow XSS if the meta tag also has an http-equiv attribute with the value "refresh". A new GODEBUG setting has been added, htmlmetacontenturlescape, which can be used to disable escaping URLs in actions in the meta content attribute which follow "url=" by setting htmlmetacontenturlescape=0. |
Go
|
| CVE-2026-27139 | Mar 06, 2026 |
go stdlib: os ReadDir/FileInfo path escape before 1.25.8 & 1.26.1On Unix platforms, when listing the contents of a directory using File.ReadDir or File.Readdir the returned FileInfo could reference a file outside of the Root in which the File was opened. The impact of this escape is limited to reading metadata provided by lstat from arbitrary locations on the filesystem without permitting reading or writing files outside the root. |
Go
|
| CVE-2025-68121 | Feb 05, 2026 |
CVE2025-68121: Go TLS Session Resumption with Mutated ClientCAs/RootCAsDuring session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake. |
Go
|
| CVE-2025-61732 | Feb 05, 2026 |
Go cgo Comment Parsing Discrepancy Enables Code SmugglingA discrepancy between how Go and C/C++ comments were parsed allowed for code smuggling into the resulting cgo binary. |
Go
|
| CVE-2025-61730 | Jan 28, 2026 |
TLS 1.3 Info Disclosure in Go TLS Library (Pre 1.22)During the TLS 1.3 handshake if multiple messages are sent in records that span encryption level boundaries (for instance the Client Hello and Encrypted Extensions messages), the subsequent messages may be processed before the encryption level changes. This can cause some minor information disclosure if a network-local attacker can inject messages during the handshake. |
Go
|
| CVE-2025-68119 | Jan 28, 2026 |
Go cmd/go <1.25.6 Local Code Exec via Malicious Version Strings in VCS ModulesDownloading and building modules with malicious version strings can cause local code execution. On systems with Mercurial (hg) installed, downloading modules from non-standard sources (e.g., custom domains) can cause unexpected code execution due to how external VCS commands are constructed. This issue can also be triggered by providing a malicious version string to the toolchain. On systems with Git installed, downloading and building modules with malicious version strings can allow an attacker to write to arbitrary files on the filesystem. This can only be triggered by explicitly providing the malicious version strings to the toolchain and does not affect usage of @latest or bare module paths. |
Go
|
| CVE-2025-47912 | Oct 29, 2025 |
URL Parse Allows NonIPv6 in Brackets Host Validation FlawThe Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement. |
Go
|
| CVE-2025-58189 | Oct 29, 2025 |
Go TLS Conn.Handshake leaks attackersupplied ALPN dataWhen Conn.Handshake fails during ALPN negotiation the error contains attacker controlled information (the ALPN protocols sent by the client) which is not escaped. |
Go
|
| CVE-2025-47906 | Sep 18, 2025 |
Go LookPath PATH bug returns execs for empty/.. inputIf the PATH environment variable contains paths which are executables (rather than just directories), passing certain strings to LookPath ("", ".", and ".."), can result in the binaries listed in the PATH being unexpectedly returned. |
Go
|
| CVE-2025-47907 | Aug 07, 2025 |
Go database/sql Scan context cancellation race conditionCancelling a query (e.g. by cancelling the context passed to one of the query methods) during a call to the Scan method of the returned Rows can result in unexpected results if other queries are being made in parallel. This can result in a race condition that may overwrite the expected results with those of another query, causing the call to Scan to return either unexpected results from the other query or an error. |
Go
|
| CVE-2025-4674 | Jul 29, 2025 |
Go Tool Command Exe via Untrusted VCS Repository ConfigThe go command may execute unexpected commands when operating in untrusted VCS repositories. This occurs when possibly dangerous VCS configuration is present in repositories. This can happen when a repository was fetched via one VCS (e.g. Git), but contains metadata for another VCS (e.g. Mercurial). Modules which are retrieved using the go command line, i.e. via "go get", are not affected. |
Go
|
| CVE-2025-0913 | Jun 11, 2025 |
Go StdLib OpenFile O_CREATE/O_EXCL Symlink Handling Fixos.OpenFile(path, os.O_CREATE|O_EXCL) behaved differently on Unix and Windows systems when the target path was a dangling symlink. On Unix systems, OpenFile with O_CREATE and O_EXCL flags never follows symlinks. On Windows, when the target path was a symlink to a nonexistent location, OpenFile would create a file in that location. OpenFile now always returns an error when the O_CREATE and O_EXCL flags are both set and the target path is a symlink. |
Go
|
| CVE-2025-22874 | Jun 11, 2025 |
Go Cert Policy Validation Bypass via VerifyOptions with ExtKeyUsageAnyCalling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon. |
Go
|
| CVE-2025-22867 | Feb 06, 2025 |
Arbitrary code exec via CGO LDFLAGS in Go1.24rc2 (Apple ld)On Darwin, building a Go module which contains CGO can trigger arbitrary code execution when using the Apple version of ld, due to usage of the @executable_path, @loader_path, or @rpath special values in a "#cgo LDFLAGS" directive. This issue only affected go1.24rc2. |
Go
|
| CVE-2025-22865 | Jan 28, 2025 |
Go ParsePKCS1PrivateKey Panic on Missing CRTUsing ParsePKCS1PrivateKey to parse a RSA key that is missing the CRT values would panic when verifying that the key is well formed. |
Go
|
| CVE-2024-34155 | Sep 06, 2024 |
Go Parse Function Stack Exhaustion via Deeply Nested LiteralsCalling any of the Parse functions on Go source code which contains deeply nested literals can cause a panic due to stack exhaustion. |
Go
|
| CVE-2024-34158 | Sep 06, 2024 |
GO Compiler Parse Panic: Stack Exhaustion via Deeply Nested //+build tagsCalling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion. |
Go
|
| CVE-2024-24791 | Jul 02, 2024 |
Go net/http Expect:100-continue mishandling before 1.20.7 leads to DDoSThe net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next request sent on the connection will fail. An attacker sending a request to a net/http/httputil.ReverseProxy proxy can exploit this mishandling to cause a denial of service by sending "Expect: 100-continue" requests which elicit a non-informational response from the backend. Each such request leaves the proxy with an invalid connection, and causes one subsequent request using that connection to fail. |
Go
|
| CVE-2024-24789 | Jun 05, 2024 |
Go archive/zip Improper Handling of Invalid ZIP Files (CVE-2024-24789)The archive/zip package's handling of certain types of invalid zip files differs from the behavior of most zip implementations. This misalignment could be exploited to create an zip file with contents that vary depending on the implementation reading the file. The archive/zip package now rejects files containing these errors. |
Go
|
| CVE-2024-24790 | Jun 05, 2024 |
Go net: IsPrivate/IsLoopback fail on IPv4-mapped IPv6 addressesThe various Is methods (IsPrivate, IsLoopback, etc) did not work as expected for IPv4-mapped IPv6 addresses, returning false for addresses which would return true in their traditional IPv4 forms. |
Go
|
| CVE-2024-3566 | Apr 10, 2024 |
CVE-2024-3566: CreateProcessBased Command Injection in Windows AppsA command inject vulnerability allows an attacker to perform command injection on Windows applications that indirectly depend on the CreateProcess function when the specific conditions are satisfied. |
Go
|
| CVE-2023-45288 | Apr 04, 2024 |
Go HTTP/2 CONTINUATION frame DoS by excessive header parsingAn attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames. Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed. This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send. The fix sets a limit on the amount of excess header frames we will process before closing a connection. |
Http2
|
| CVE-2023-45290 | Mar 05, 2024 |
Go net/http ParseMultipartForm Mem Exhaustion using Long Form LinesWhen parsing a multipart form (either explicitly with Request.ParseMultipartForm or implicitly with Request.FormValue, Request.PostFormValue, or Request.FormFile), limits on the total size of the parsed form were not applied to the memory consumed while reading a single form line. This permits a maliciously crafted input containing very long lines to cause allocation of arbitrarily large amounts of memory, potentially leading to memory exhaustion. With fix, the ParseMultipartForm function now correctly limits the maximum size of form lines. |
Go
|
| CVE-2023-48795 | Dec 18, 2023 |
OpenSSH <9.6 BPP handshake flaw allows integrity bypass (Terrapin attack)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 handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before 1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, LANCOM LCOS and LANconfig, FileZilla before 3.66.4, Nova before 11.8, PKIX-SSH before 14.4, SecureCRT before 9.4.3, Transmit5 before 5.10.4, Win32-OpenSSH before 9.5.0.0p1-Beta, WinSCP before 6.2.2, Bitvise SSH Server before 9.32, Bitvise SSH Client before 9.33, KiTTY through 0.76.1.13, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust. |
Crypto
|
| CVE-2023-39326 | Dec 06, 2023 |
Go net/http Chunked Reader Vulnerability: HTTP Chunk Extension OverreadA malicious HTTP sender can use chunk extensions to cause a receiver reading from a request or response body to read many more bytes from the network than are in the body. A malicious HTTP client can further exploit this to cause a server to automatically read a large amount of data (up to about 1GiB) when a handler fails to read the entire body of a request. Chunk extensions are a little-used HTTP feature which permit including additional metadata in a request or response body sent using the chunked encoding. The net/http chunked encoding reader discards this metadata. A sender can exploit this by inserting a large metadata segment with each byte transferred. The chunk reader now produces an error if the ratio of real body to encoded bytes grows too small. |
Go
|
| CVE-2023-45285 | Dec 06, 2023 |
Go Modules .git Suffix Causes Insecure git:// FallbackUsing go get to fetch a module with the ".git" suffix may unexpectedly fallback to the insecure "git://" protocol if the module is unavailable via the secure "https://" and "git+ssh://" protocols, even if GOINSECURE is not set for said module. This only affects users who are not using the module proxy and are fetching modules directly (i.e. GOPROXY=off). |
Go
|
| CVE-2023-45287 | Dec 05, 2023 |
Go TLS RSA Timing SideChannel vulnerability before 1.20Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits. In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels. |
Go
|
| CVE-2023-45284 | Nov 09, 2023 |
MS Windows IsLocal Function Fails to Detect Reserved Device Names (CVE-2023-45284)On Windows, The IsLocal function does not correctly detect reserved device names in some cases. Reserved names followed by spaces, such as "COM1 ", and reserved names "COM" and "LPT" followed by superscript 1, 2, or 3, are incorrectly reported as local. With fix, IsLocal now correctly reports these names as non-local. |
Go
|
| CVE-2023-45283 | Nov 09, 2023 |
Go filepath RLD path issue (1.20.11/1.21.4)The filepath package does not recognize paths with a \??\ prefix as special. On Windows, a path beginning with \??\ is a Root Local Device path equivalent to a path beginning with \\?\. Paths with a \??\ prefix may be used to access arbitrary locations on the system. For example, the path \??\c:\x is equivalent to the more common path c:\x. Before fix, Clean could convert a rooted path such as \a\..\??\b into the root local device path \??\b. Clean will now convert this to .\??\b. Similarly, Join(\, ??, b) could convert a seemingly innocent sequence of path elements into the root local device path \??\b. Join will now convert this to \.\??\b. In addition, with fix, IsAbs now correctly reports paths beginning with \??\ as absolute, and VolumeName correctly reports the \??\ prefix as a volume name. UPDATE: Go 1.20.11 and Go 1.21.4 inadvertently changed the definition of the volume name in Windows paths starting with \?, resulting in filepath.Clean(\?\c:) returning \?\c: rather than \?\c:\ (among other effects). The previous behavior has been restored. |
Go
|
| CVE-2023-29453 | Oct 12, 2023 |
Go Templates unescaped backticks pre-1.21JS injectionTemplates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected. Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template. As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g., "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml. With fix, Template. Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported but will be exported in the release of Go 1.21. Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution. |
Go
|
| CVE-2023-39325 | Oct 11, 2023 |
Go HTTP/2 Server Resource Exhaustion via Rapid Reset RacesA malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing. With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection. This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2. The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function. |
Http2
Go
|
| CVE-2023-44487 | Oct 10, 2023 |
HTTP/2 DoS via Stream Reset in nginxThe HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023. |
Http2
Go
Networking
And others... |
| CVE-2023-39323 | Oct 05, 2023 |
Go Compiler Line Directive Exploit Bypasses cgo RestrictionsLine directives ("//line") can be used to bypass the restrictions on "//go:cgo_" directives, allowing blocked linker and compiler flags to be passed during compilation. This can result in unexpected execution of arbitrary code when running "go build". The line directive requires the absolute path of the file in which the directive lives, which makes exploiting this issue significantly more complex. |
Go
|
| CVE-2023-39320 | Sep 08, 2023 |
Go 1.21 Toolchain RCE via go.modThe go.mod toolchain directive, introduced in Go 1.21, can be leveraged to execute scripts and binaries relative to the root of the module when the "go" command was executed within the module. This applies to modules downloaded using the "go" command from the module proxy, as well as modules downloaded directly using VCS software. |
Go
|
| CVE-2023-39319 | Sep 08, 2023 |
Go html/template XSS via improper script handlingThe html/template package does not apply the proper rules for handling occurrences of "<script", "<!--", and "</script" within JS literals in <script> contexts. This may cause the template parser to improperly consider script contexts to be terminated early, causing actions to be improperly escaped. This could be leveraged to perform an XSS attack. |
Go
|
| CVE-2023-39318 | Sep 08, 2023 |
Go html/template XSS from mishandled comment tokens in <script> tagsThe html/template package does not properly handle HTML-like "" comment tokens, nor hashbang "#!" comment tokens, in <script> contexts. This may cause the template parser to improperly interpret the contents of <script> contexts, causing actions to be improperly escaped. This may be leveraged to perform an XSS attack. |
Go
|
| CVE-2023-39321 | Sep 08, 2023 |
quic-go Incomplete Post-Handshake Message Panic (CVE-2023-39321)Processing an incomplete post-handshake message for a QUIC connection can cause a panic. |
Go
|
| CVE-2023-39322 | Sep 08, 2023 |
Unbounded memory growth via oversized QUIC posthandshake messagesQUIC connections do not set an upper bound on the amount of data buffered when reading post-handshake messages, allowing a malicious QUIC connection to cause unbounded memory growth. With fix, connections now consistently reject messages larger than 65KiB in size. |
Go
|
| CVE-2023-39533 | Aug 08, 2023 |
Resource Exhaustion via Large RSA Keys in go-libp2p <0.27.8 <0.28.2 <0.29.1go-libp2p is the Go implementation of the libp2p Networking Stack. Prior to versions 0.27.8, 0.28.2, and 0.29.1 malicious peer can use large RSA keys to run a resource exhaustion attack & force a node to spend time doing signature verification of the large key. This vulnerability is present in the core/crypto module of go-libp2p and can occur during the Noise handshake and the libp2p x509 extension verification step. To prevent this attack, go-libp2p versions 0.27.8, 0.28.2, and 0.29.1 restrict RSA keys to <= 8192 bits. To protect one's application, it is necessary to update to these patch releases and to use the updated Go compiler in 1.20.7 or 1.19.12. There are no known workarounds for this issue. |
Go
|