p PatchFirst

PatchFirst · Latest vulnerabilities

go vulnerabilities

Vulnerabilities published for go in the last 30 days: 11. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 196

  1. CVE-2026-97054

    Medium · CVSS 5.9EPSS 0.48%Fix available

    HTTP/1 server crash due to MaxBytesReader header race in net/http

    For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. As a result, an HTTP/1 server that utilizes MaxBytesReader or MaxBytesHandler can crash due to runtime panic if its handler reads the request body concurrently with writing the response header.

    • Update to 1.26.11-r0
    Published Updated
  2. CVE-2026-97033

    High · CVSS 8.8EPSS 0.69%Fix available

    Unexpected code execution via --sysroot, -target, -isysroot, -Wl,-syslibroot, and -x cgo flags in cmd/go

    Building a malicious package that uses cgo could cause arbitrary code execution at build time through several compiler and linker flags permitted in "#cgo" directives. Specifically, "--sysroot" in GCC and Clang relocates compiler subprograms, spec files, and CRT startup objects to an attacker-controlled directory; "-target" in Clang falls back to executing target helper tools from the current working directory when not found in PATH; "-isysroot" and "-Wl,-syslibroot" can pass a regular file on disk to GNU ld.bfd, which interprets it as a positional linker script; and "-x" permitted specifying arbitrary compiler input languages beyond those su

    • Update to 1.26.11-r0
    Published Updated
  3. CVE-2026-97034

    High · CVSS 8.8EPSS 0.83%Fix available

    Arbitrary command execution via GCC spec files in cgo linker search directories in cmd/go

    When using GCC, building a malicious package that uses cgo could cause arbitrary command execution at link time via untrusted GCC spec files ("specs" or "*.spec"). When linking with "-fopenmp", "-fopenacc", or "-fsanitize=" in "#cgo LDFLAGS", GCC's built-in link spec evaluates "%:include(libgomp.spec)" or "%:include(libsanitizer.spec)" and searches for spec files in "-L" and sysroot directories (including subdirectories and multilib sibling directories such as "../lib64"), as well as the working directory when "-fopenmp" or "-fopenacc" is used or when "-fsanitize=" is combined with "-static" or "-static-lib*". The go command now rejects "-L",

    • Update to 1.26.11-r0
    Published Updated
  4. CVE-2026-97035

    High · CVSS 8.8EPSS 0.71%Fix available

    Unexpected code execution and arbitrary file write via Clang -gen-* and GCC -gnat* flags in cgo in cmd/go

    When using Clang or GCC, building a malicious package that uses cgo could cause unexpected code execution at build time or write files to arbitrary directories via "-gen-*" or "-gnat*" flags in "#cgo" directives. The "-g*" wildcard in the compiler and linker flag allowlists previously matched Clang's two-argument "-gen-cdb-fragment-path <dir>" flag and GCC's two-argument "-gnatO <file>" flag, permitting compilation database fragments and sidecar output files to be written to arbitrary directories and desynchronizing flag argument parsing between the go command and the compiler driver so that subsequent arguments could be passed as unvalidated

    • Update to 1.26.11-r0
    Published Updated
  5. CVE-2026-97037

    High · CVSS 8.8EPSS 0.69%Fix available

    Linker script injection via split -Wl, flags and Darwin or symbol linker flags in cgo in cmd/go

    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 "-Wl,-undefined") previously accepted a bare second argument without a "-Wl," prefix, which the compiler driver passes directly to the linker as a positional input file. Additionally, when using GNU ld.bfd, flags such as "-framework", "-Wl,-framework", "-Wl,-undefined", "-Wl,--just-symbols", "-Wl,-R", "-Wl,-subsystem", and (on non-Darwin platforms) "-Wl,-sectcreate" could cause ld.b

    • Update to 1.26.11-r0
    Published Updated
  6. CVE-2026-97038

    High · CVSS 8.8EPSS 0.69%Fix available

    Arbitrary code execution via crafted .syso files and cgo linker input files in cmd/go

    Building a malicious package containing ".syso" files or cgo linker inputs could inject arbitrary linker flags or execute arbitrary code at link time. Linker input files—including ".syso" files, direct object or library inputs in "#cgo LDFLAGS", and libraries in "-L" directories—were passed to the external linker without validating their format or checking for embedded linker options. Across platforms, this allowed executing GNU ld implicit linker scripts disguised as libraries or ".syso" files (or loaded via "-l:<filename>" or "-l" containing path separators), injecting unallowlisted linker flags via PE/COFF ".drectve" sections on Windows or

    • Update to 1.26.11-r0
    Published Updated
  7. CVE-2026-97039

    High · CVSS 8.3EPSS 0.49%Fix available

    Flag sanitization bypass via "#cgo pkg-config:" directives in cmd/go

    Building a malicious package that uses "#cgo pkg-config:" directives could load untrusted pkg-config ".pc" files or inject unvalidated compiler and linker flags. The pkg-config flag allowlist previously permitted "--with-path=" and "--personality=", allowed "--define-variable=" values beginning with "=" or "$" (which can rewrite paths in system ".pc" files into sysroot-prefixed "-L=" or "-L$SYSROOT" linker search paths), and allowed package arguments ending in ".pc" or containing path separators or "..", which caused pkg-config to load local ".pc" files directly from the package directory. In addition, flags returned by "pkg-config --cflags"

    • Update to 1.26.11-r0
    Published Updated
  8. CVE-2026-97040

    Critical · CVSS 9.8EPSS 0.8%Fix available

    Cgo directive injection via .syso files disguised as Go object files in cmd/go and cmd/link

    Building a package containing a crafted ".syso" file could bypass cgo flag validation and inject arbitrary linker flags when linking. When loading ".syso" entries from a package archive, the linker only checked for recognized host object headers (ELF, Mach-O, PE, and XCOFF) before falling through to Go object parsing. A ".syso" file beginning with a "go object" header was parsed as a Go compiler object, allowing untrusted cgo metadata directives (such as "cgo_ldflag" or "cgo_dynamic_linker") embedded in the ".syso" file to be passed to the external linker without validation. Additionally, ".syso" filenames longer than 16 bytes lost their ".sy

    • Update to 1.26.11-r0
    Published Updated
  9. CVE-2026-97041

    High · CVSS 8.8EPSS 0.57%Fix available

    Host linker flag injection via //go:cgo_* directives in cmd/compile and cmd/link

    Building a malicious package containing "//go:cgo_*" compiler directives could inject arbitrary flags into the external linker invocation on ELF platforms. The compiler and linker did not reject commas in "//go:cgo_import_dynamic", "//go:cgo_export_dynamic", "//go:cgo_export_static", "//go:cgo_import_static", and "//go:cgo_dynamic_linker" directives, and the linker passed the dynamic linker path using "-Wl,--dynamic-linker,<path>". Furthermore, the two-argument form of "//go:cgo_import_dynamic" (which is permitted in non-cgo Go source files) could overwrite the external symbol name of a symbol already marked for cgo export. A symbol name or d

    • Update to 1.26.11-r0
    Published Updated
  10. CVE-2026-97042

    High · CVSS 8.8EPSS 0.57%Fix available

    Linker flag injection via cgo_import_dynamic and PE DLL names in cmd/cgo, cmd/compile, and cmd/link

    Building a malicious package that uses "//go:cgo_import_dynamic" or links against a crafted PE object on Windows could pass unsafe library arguments to the external linker. The compiler only checked the first character of the library name in "//go:cgo_import_dynamic" directives and skipped validation in cgo-generated files. In addition, on Windows, "cmd/cgo" and "cmd/link" did not validate imported DLL names extracted from PE object files before emitting "-l<name>" flags for the external linker, allowing a crafted DLL name containing ".." path traversal or special characters to reference arbitrary files on disk. The compiler now validates eve

    • Update to 1.26.11-r0
    Published Updated
  11. CVE-2026-97043

    High · CVSS 8.8EPSS 0.72%Fix available

    Unexpected code execution via escaped quotes in //go:cgo_ldflag in cmd/go and cmd/compile

    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 "#cgo LDFLAGS" argument with strconv.Quote in a "//go:cgo_ldflag" directive, but "cmd/compile" and "cmd/go" parsed those directives by splitting on raw quote characters without handling backslash escapes or unquoting the string. This mismatch allowed disallowed linker flags or unvalidated linker search paths to be smuggled past the go command's flag checks and passed t

    • Update to 1.26.11-r0
    Published Updated
  12. CVE-2026-111943

    Medium · CVSS 6.8EPSS 0.5%Public exploitFix available

    Distrust compromised intermediate certificates in crypto/x509

    On most platforms, Go uses the given system root certificates. However, in some narrower cases, the system trust stores may not be updated without further action. To defend against the narrower set of cases that may remain affected, a denylist was added in crypto/x509 to return an error when calling Verify with any of the known intermediate certificates that are no longer considered to be trustworthy.

    • Update to 1.26.10-r0
    Published Updated
  13. CVE-2026-97032

    High · CVSS 7.5EPSS 0.65%Fix available

    HTTP/2 server crash due to HPACK encoder race in net/http

    HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.

    • Update to 1.26.9-r0
    Published Updated
  14. CVE-2026-94439

    High · CVSS 7.5EPSS 0.62%Fix available

    HTTP/1 server connection desynchronization after 2xx CONNECT response in net/http

    When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. Since a 2xx response to an HTTP/1 CONNECT converts the connection into a tunnel, the server should not treat the connection as continuing to contain HTTP. The impact of this misbehavior is mostly limited to potential request smuggling, where an intermediate proxy considers the data on the connection to be tunneled and the server considers it to be HTTP.

    • Update to 1.26.9-r0
    Published Updated
  15. CVE-2026-78663

    Critical · CVSS 9.1EPSS 0.83%Fix available

    Double flow control refund on HTTP/2 server streams in net/http

    The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection). Total buffered data is still limited by the concurrent stream limit and stream-level flow control.

    • Update to 1.26.9-r0
    Published Updated
  16. CVE-2026-78669

    High · CVSS 7.5EPSS 0.82%Fix available

    Excessive CPU consumption from repeated initial window changes in net/http

    A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values.

    • Update to 1.26.9-r0
    Published Updated
  17. CVE-2026-78660

    High · CVSS 7.5EPSS 0.52%Fix available

    HTTP/2 transport accepts malformed framing-related headers in net/http

    Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling.

    • Update to 1.26.9-r0
    Published Updated
  18. CVE-2026-97031

    High · CVSS 7.5EPSS 0.72%Fix available

    Reject malformed ECH outer extension references in crypto/tls

    Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.

    • Update to 1.26.9-r0
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →