NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
180 matching advisories · page 1 of 6Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.6 CVE-2026-116641 The DB Tools rely on the TLS implementation in Golang’s standard library, which generally uses the system CA store. MONGODB · Database Tools 24 days ago high8.8 CVE-2026-116676 Atlantis is a self-hosted golang application that listens for Terraform pull request events via webhooks. go · github.com/runatlantis/atlantis 25 days ago high7.8 CVE-2026-94447 Previously, a user operating inside of a malicious Go project that defines a bogus golang.org/toolchain go.sum entry and operates a malicious GOMODPROXY the us… 44 days ago high7.8 CVE-2026-94444 Previously, a user operating inside of a malicious Go project that defines a bogus golang.org/fips140 and operates a malicious GOMODPROXY the user chooses to c… 44 days ago high8.7 CVE-2026-84445 gRPC-Go xDS servers: Denial of Service (DoS) via crash due to missing `:authority` and `Host` headers go · google.golang.org/grpc 2026-09-08 high7.5 CVE-2026-78662 Previously, a channel registered in the mux's chanList is not usable until it is established. golang · crypto 2026-09-02 high7.5 CVE-2026-56855 Previously, after a channel has been established, a malicious peer could send crafted messages that would deadlock the entire connection. golang · crypto 2026-09-02 high8.7 CVE-2026-84304 gRPC-Go: Heap Memory Exhaustion (OOM) via HTTP/2 DATA Frame Fragmentation go · google.golang.org/grpc 2026-09-01 high8.1 CVE-2026-64679 Atlantis is a self-hosted golang application that listens for Terraform pull request events via webhooks. go · github.com/runatlantis/atlantis 2026-08-21 high7.5 CVE-2026-46603 VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree gr… 2026-08-14 high8.8 GHSA-hrxh-6v49-42gf gRPC-Go: xDS RBAC and HTTP/2 Vulnerabilities go · google.golang.org/grpc 2026-07-21 high7.8 CVE-2026-39822 On Unix systems, opening a file in an os.Root improperly follows symlinks to locations outside of the Root when the final path component of the a path is a sym… golang · go 2026-07-08 high7.5 CVE-2026-46604 The TIFF decoder can panic when decoding an invalid image with an out-of-bounds strip offset. golang · tiff 2026-06-26 high7.5 CVE-2026-46599 golang.org/x/image/tiff has excessive resource consumption in PackBits decompression go · golang.org/x/image 2026-05-29 high7.5 CVE-2026-46597 An incorrectly placed cast from bytes to int allowed for server-side panic in the AES-GCM packet decoder for well-crafted inputs. go · golang.org/x/crypto 2026-05-22 high7.5 CVE-2026-39829 The RSA and DSA public key parsers did not enforce size limits on key parameters. go · golang.org/x/crypto 2026-05-22 high7.5 CVE-2026-42501 A malicious module proxy can exploit a flaw in the go command's validation of module checksums to bypass checksum database validation. golang · go 2026-05-07 high7.5 CVE-2026-42499 Pathological inputs could cause DoS through consumePhrase when parsing an email address according to RFC 5322. golang · go 2026-05-07 high7.5 CVE-2026-39836 The Dial and LookupPort functions panic on Windows when provided with an input containing a NUL (0). golang · go 2026-05-07 high7.5 CVE-2026-39820 Well-crafted inputs reaching ParseAddress, ParseAddressList, and ParseDate were able to trigger excessive CPU exhaustion and memory allocations. golang · go 2026-05-07 high7.5 CVE-2026-33814 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 va… golang · go, golang · http2 2026-05-07 high7.5 CVE-2026-33811 When using LookupCNAME with the cgo DNS resolver, a very long CNAME response can trigger a double-free of C memory and a crash. golang · go 2026-05-07 high8.8 CVE-2026-42503 gopls by default communicates via pipe. golang · gopls 2026-05-06 high7.5 CVE-2026-33813 Parsing a WEBP image with an invalid, large size panics on 32-bit platforms. golang · image 2026-04-21 high8.2 CVE-2026-33810 When verifying a certificate chain containing excluded DNS constraints, these constraints are not correctly applied to wildcard DNS SANs which use a different … golang · go 2026-04-08 high7.5 CVE-2026-32283 If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consu… golang · go 2026-04-08 high7.5 CVE-2026-32281 Validating certificate chains which use policies is unexpectedly inefficient when certificates in the chain contain a very large number of policy mappings, pos… golang · go 2026-04-08 high7.5 CVE-2026-32280 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.In… golang · go 2026-04-08 high7.1 CVE-2026-27144 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 d… golang · go 2026-04-08 high8.8 CVE-2026-27140 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. golang · go 2026-04-08

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.