Golang

Go

170 Schwachstellen gefunden.

Hinweis: Diese Liste kann unvollständig sein. Daten werden ohne Gewähr im Ursprungsformat bereitgestellt.
  • EPSS 0.02%
  • Veröffentlicht 07.05.2026 19:41:17
  • Zuletzt bearbeitet 13.05.2026 14:41:59

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.

  • EPSS 0.02%
  • Veröffentlicht 08.04.2026 01:06:58
  • Zuletzt bearbeitet 16.04.2026 19:16:42

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

  • EPSS 0.02%
  • Veröffentlicht 08.04.2026 01:06:58
  • Zuletzt bearbeitet 16.04.2026 19:15:57

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

  • EPSS 0.02%
  • Veröffentlicht 08.04.2026 01:06:57
  • Zuletzt bearbeitet 16.04.2026 19:26:59

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.

  • EPSS 0.02%
  • Veröffentlicht 08.04.2026 01:06:57
  • Zuletzt bearbeitet 16.04.2026 19:20:02

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.

  • EPSS 0.02%
  • Veröffentlicht 08.04.2026 01:06:57
  • Zuletzt bearbeitet 16.04.2026 19:12:10

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.

  • EPSS 0%
  • Veröffentlicht 08.04.2026 01:06:57
  • Zuletzt bearbeitet 16.04.2026 19:08:52

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.

  • EPSS 0.01%
  • Veröffentlicht 08.04.2026 01:06:56
  • Zuletzt bearbeitet 16.04.2026 19:17:18

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

  • EPSS 0.01%
  • Veröffentlicht 08.04.2026 01:06:56
  • Zuletzt bearbeitet 16.04.2026 19:06:57

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

  • EPSS 0.01%
  • Veröffentlicht 08.04.2026 01:06:56
  • Zuletzt bearbeitet 20.04.2026 18:16:26

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