NetSight

Security Dashboard

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

Reset
331 matching advisories · page 3 of 12Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.1 CVE-2026-6290 Velociraptor versions prior to 0.76.3 contain a vulnerability in the query() plugin which allows access to all orgs with the user's current ACL token. go · www.velocidex.com/golang/velociraptor 2026-04-15 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 medium6.1 CVE-2026-32289 Context was not properly tracked across template branches for JS template literals, leading to possibly incorrect escaping of content when branches were used. golang · go 2026-04-08 medium5.5 CVE-2026-32288 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 "ol… 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 medium6.4 CVE-2026-32282 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… 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 critical9.8 CVE-2026-27143 Arithmetic over induction variables in loops were not correctly checked for underflow or overflow. 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 medium5.3 CVE-2026-33809 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-m… go · golang.org/x/image 2026-03-25 critical9.1 CVE-2026-33186 gRPC-Go has an authorization bypass via missing leading slash in :path go · google.golang.org/grpc 2026-03-18 medium6.1 CVE-2026-27142 Actions which insert URLs into the content attribute of HTML meta tags are not escaped. golang · go 2026-03-06 low2.5 CVE-2026-27139 On Unix platforms, when listing the contents of a directory using File.ReadDir or File.Readdir the returned FileInfo could reference a file outside of the Root… golang · go 2026-03-06 medium5.9 CVE-2026-27138 Certificate verification can panic when a certificate in the chain has an empty DNS name and another certificate in the chain has excluded name constraints. golang · go 2026-03-06 high7.5 CVE-2026-27137 When verifying a certificate chain which contains a certificate containing multiple email address constraints which share common local portions but different d… golang · go 2026-03-06 high7.5 CVE-2026-25679 url.Parse insufficiently validated the host/authority component and accepted some invalid URLs. golang · go 2026-03-06 high7.5 CVE-2026-26315 go-ethereum (Geth) is a golang execution layer implementation of the Ethereum protocol. go · github.com/ethereum/go-ethereum 2026-02-18 high7.5 CVE-2026-26314 go-ethereum (geth) is a golang execution layer implementation of the Ethereum protocol. go · github.com/ethereum/go-ethereum 2026-02-18 high7.5 CVE-2026-26313 go-ethereum (geth) is a golang execution layer implementation of the Ethereum protocol. go · github.com/ethereum/go-ethereum 2026-02-18 critical10.0 CVE-2025-68121 During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed han… golang · go 2026-02-05 medium5.3 CVE-2025-58190 The html.Parse function in golang.org/x/net/html has an infinite parsing loop when processing certain inputs, which can lead to denial of service (DoS) if an a… go · html 2026-02-05 medium5.3 CVE-2025-47911 The html.Parse function in golang.org/x/net/html has quadratic parsing complexity when processing certain inputs, which can lead to denial of service (DoS) if … go · golang.org/x/net/html 2026-02-05 high8.6 CVE-2025-61732 A discrepancy between how Go and C/C++ comments were parsed allowed for code smuggling into the resulting cgo binary. golang · go 2026-02-05 low3.8 CVE-2025-22873 It was possible to improperly access the parent directory of an os.Root by opening a filename ending in "../". golang · go 2026-02-04 high7.0 CVE-2025-68119 Downloading and building modules with malicious version strings can cause local code execution. golang · go 2026-01-28 high7.8 CVE-2025-61731 Building a malicious file with cmd/go can cause can cause a write to an attacker-controlled file with partial control of the file content. golang · go 2026-01-28 medium5.3 CVE-2025-61730 During the TLS 1.3 handshake if multiple messages are sent in records that span encryption level boundaries (for instance the Client Hello and Encrypted Extens… golang · go 2026-01-28 medium6.5 CVE-2025-61728 archive/zip uses a super-linear file name indexing algorithm that is invoked the first time a file in an archive is opened. golang · go 2026-01-28

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.