VYPR

Go

by Golang

Source repositories

CVEs (233)

  • CVE-2026-97043HigNov 11, 2026
    risk 0.50cvss 8.8epss 0.01

    Building a malicious package that uses cgo could bypass "#cgo LDFLAGS" validation and cause unexpected code execution at build time, or cause the go command to panic, via crafted quoting in "//go:cgo_ldflag" directives. When "cmd/cgo" generates "_cgo_gotypes.go", it quotes each…

  • CVE-2026-97037HigNov 11, 2026
    risk 0.50cvss 8.8epss 0.01

    Building a malicious package that uses cgo could cause arbitrary code execution at link time by passing linker script files to the host linker via "#cgo LDFLAGS". Split "-Wl," flags that consume a following argument (such as "-Wl,-rpath", "-Wl,--just-symbols", and…

  • CVE-2026-27140HigApr 8, 2026
    risk 0.50cvss 8.8epss 0.01

    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-2024-45340HigJan 28, 2025
    risk 0.50cvss 8.8epss 0.01

    Credentials provided via the new GOAUTH feature were not being properly segmented by domain, allowing a malicious server to request credentials they should not have access to. By default, unless otherwise set, this only affected credentials stored in the users .netrc file.

  • CVE-2022-24675HigApr 20, 2022
    risk 0.50cvss 7.5epss 0.10

    encoding/pem in Go before 1.17.9 and 1.18.x before 1.18.1 has a Decode stack overflow via a large amount of PEM data.

  • CVE-2026-46600HigJul 21, 2026
    risk 0.49cvss 7.5epss 0.01

    Parsing an invalid SVCB or HTTPS RR can panic when the size of a parameter value overflows the message buffer.

  • CVE-2025-61732HigFeb 5, 2026
    risk 0.49cvss 8.6epss 0.01

    A discrepancy between how Go and C/C++ comments were parsed allowed for code smuggling into the resulting cgo binary.

  • CVE-2025-61729HigDec 2, 2025
    risk 0.49cvss 7.5epss 0.00

    Within HostnameError.Error(), when constructing an error string, there is no limit to the number of hosts that will be printed out. Furthermore, the error string is constructed by repeated string concatenation, leading to quadratic runtime. Therefore, a certificate provided by a…

  • CVE-2025-4674HigJul 29, 2025
    risk 0.49cvss 8.6epss 0.00

    The 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…

  • CVE-2023-45285HigDec 6, 2023
    risk 0.49cvss 7.5epss 0.01

    Using 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…

  • CVE-2023-45287HigDec 5, 2023
    risk 0.49cvss 7.5epss 0.01

    Before 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…

  • CVE-2023-45283HigNov 9, 2023
    risk 0.49cvss 7.5epss 0.03

    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…

  • CVE-2023-39325HigOct 11, 2023
    risk 0.49cvss 7.5epss 0.04

    A 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…

  • CVE-2023-39322HigSep 8, 2023
    risk 0.49cvss 7.5epss 0.01

    QUIC 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.

  • CVE-2023-39321HigSep 8, 2023
    risk 0.49cvss 7.5epss 0.01

    Processing an incomplete post-handshake message for a QUIC connection can cause a panic.

  • CVE-2023-24537HigApr 6, 2023
    risk 0.49cvss 7.5epss 0.01

    Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow.

  • CVE-2023-24536HigApr 6, 2023
    risk 0.49cvss 7.5epss 0.01

    Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts. This stems from several causes: 1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can…

  • CVE-2023-24534HigApr 6, 2023
    risk 0.49cvss 7.5epss 0.02

    HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service. Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more…

  • CVE-2022-41725HigFeb 28, 2023
    risk 0.49cvss 7.5epss 0.01

    A denial of service is possible from excessive resource consumption in net/http and mime/multipart. Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package…

  • CVE-2022-41724HigFeb 28, 2023
    risk 0.49cvss 7.5epss 0.01

    Large handshake records may cause panics in crypto/tls. Both clients and servers may send large TLS handshake records which cause servers and clients, respectively, to panic when attempting to construct responses. This affects all TLS 1.3 clients, TLS 1.2 clients which…

Page 3 of 12