Filtered by vendor Golang
Subscribe
Total
219 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2026-39823 | 1 Golang | 1 Go | 2026-05-13 | N/A | 6.1 MEDIUM |
| CVE-2026-27142 fixed a vulnerability in which URLs were not correctly escaped inside of a <meta> tag's <content> attribute. If the URL content were to insert ASCII whitespaces around the '=' rune inside of the <content> attribute, the escaper would fail to similarly escape it, leading to XSS. | |||||
| CVE-2026-33813 | 1 Golang | 1 Image | 2026-05-13 | N/A | 7.5 HIGH |
| Parsing a WEBP image with an invalid, large size panics on 32-bit platforms. | |||||
| CVE-2026-39836 | 1 Golang | 1 Go | 2026-05-13 | N/A | 7.5 HIGH |
| The Dial and LookupPort functions panic on Windows when provided with an input containing a NUL (0). | |||||
| CVE-2026-39820 | 1 Golang | 1 Go | 2026-05-13 | N/A | 7.5 HIGH |
| Well-crafted inputs reaching ParseAddress, ParseAddressList, and ParseDate were able to trigger excessive CPU exhaustion and memory allocations. | |||||
| CVE-2026-39819 | 1 Golang | 1 Go | 2026-05-13 | N/A | 5.3 MEDIUM |
| The "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. | |||||
| CVE-2026-39817 | 1 Golang | 1 Go | 2026-05-13 | N/A | 5.9 MEDIUM |
| 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. | |||||
| CVE-2026-33814 | 1 Golang | 2 Go, Http2 | 2026-05-13 | N/A | 7.5 HIGH |
| When 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. | |||||
| CVE-2026-33811 | 1 Golang | 1 Go | 2026-05-12 | N/A | 7.5 HIGH |
| When using LookupCNAME with the cgo DNS resolver, a very long CNAME response can trigger a double-free of C memory and a crash. | |||||
| CVE-2026-33809 | 1 Golang | 1 Tiff | 2026-04-21 | N/A | 5.3 MEDIUM |
| A maliciously crafted TIFF file can cause image decoding to attempt to allocate up 4GiB of memory, causing either excessive resource consumption or an out-of-memory error. | |||||
| CVE-2026-33810 | 1 Golang | 1 Go | 2026-04-20 | N/A | 8.2 HIGH |
| When verifying a certificate chain containing excluded DNS constraints, these constraints are not correctly applied to wildcard DNS SANs which use a different case than the constraint. 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. | |||||
| CVE-2026-27140 | 1 Golang | 1 Go | 2026-04-16 | N/A | 8.8 HIGH |
| SWIG 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. | |||||
| CVE-2026-27143 | 1 Golang | 1 Go | 2026-04-16 | N/A | 9.8 CRITICAL |
| Arithmetic 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. | |||||
| CVE-2026-27144 | 1 Golang | 1 Go | 2026-04-16 | N/A | 7.1 HIGH |
| The 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. | |||||
| CVE-2026-32280 | 1 Golang | 1 Go | 2026-04-16 | N/A | 7.5 HIGH |
| 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. | |||||
| CVE-2026-32281 | 1 Golang | 1 Go | 2026-04-16 | N/A | 7.5 HIGH |
| Validating 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. | |||||
| CVE-2026-32282 | 1 Golang | 1 Go | 2026-04-16 | N/A | 6.4 MEDIUM |
| On Linux, if the target of Root.Chmod is replaced with a symlink while the chmod operation is in progress, Chmod can operate on the target of the symlink, even when the target lies outside the root. The Linux fchmodat syscall silently ignores the AT_SYMLINK_NOFOLLOW flag, which Root.Chmod uses to avoid symlink traversal. Root.Chmod checks its target before acting and returns an error if the target is a symlink lying outside the root, so the impact is limited to cases where the target is replaced with a symlink between the check and operation. | |||||
| CVE-2026-32283 | 1 Golang | 1 Go | 2026-04-16 | N/A | 7.5 HIGH |
| If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consumption of resources. This can lead to a denial of service. This only affects TLS 1.3. | |||||
| CVE-2026-32288 | 1 Golang | 1 Go | 2026-04-16 | N/A | 5.5 MEDIUM |
| tar.Reader can allocate an unbounded amount of memory when reading a maliciously-crafted archive containing a large number of sparse regions encoded in the "old GNU sparse map" format. | |||||
| CVE-2026-32289 | 1 Golang | 1 Go | 2026-04-16 | N/A | 6.1 MEDIUM |
| Context was not properly tracked across template branches for JS template literals, leading to possibly incorrect escaping of content when branches were used. Additionally template actions within JS template literals did not properly track the brace depth, leading to incorrect escaping being applied. These issues could cause actions within JS template literals to be incorrectly or improperly escaped, leading to XSS vulnerabilities. | |||||