NetSight

Security Dashboard

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

Reset
37 matching advisories · page 1 of 2Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-pg3x-5c63-5pvw Malicious code in golangtw (npm)Malware npm · golangtw 2026-09-13 critical9.6 CVE-2026-39821 The ToASCII and ToUnicode functions incorrectly accept Punycode-encoded labels that decode to an ASCII-only label. golang · net 2026-05-22 critical10.0 CVE-2026-46595 Previously, CVE-2024-45337 fixed an authorization bypass for misused ssh server configurations; if any other type of callback is passed other than public key, … go · golang.org/x/crypto 2026-05-22 critical9.1 CVE-2026-42508 Previously, a revoked 'SignatureKey' belonging to a CA was not correctly checked for revocation. go · golang.org/x/crypto 2026-05-22 critical9.1 CVE-2026-39834 When writing data larger than 4GB in a single Write call on an SSH channel, an integer overflow in the internal payload size calculation caused the write loop … go · golang.org/x/crypto 2026-05-22 critical9.1 CVE-2026-39833 The in-memory keyring returned by NewKeyring() silently accepted keys with the ConfirmBeforeUse constraint but never enforced it. go · golang.org/x/crypto 2026-05-22 critical9.1 CVE-2026-39832 When adding a key to a remote agent constraint extensions such as restrict-destination-v00@openssh.com were not serialized in the request. go · golang.org/x/crypto 2026-05-22 critical9.1 CVE-2026-39831 The Verify() method for FIDO/U2F security key types (sk-ecdsa-sha2-nistp256@openssh.com, sk-ssh-ed25519@openssh.com) did not check the User Presence flag. go · golang.org/x/crypto 2026-05-22 critical9.1 CVE-2026-39830 A malicious SSH peer could send unsolicited global request responses to fill an internal buffer, blocking the connection's read loop. go · golang.org/x/crypto 2026-05-22 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 critical9.8 CVE-2026-27143 Arithmetic over induction variables in loops were not correctly checked for underflow or overflow. golang · go 2026-04-08 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 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 critical GHSA-3xq6-jchq-ph3r Malware in @ctrl/golang-templateMalware npm · @ctrl/golang-template 2025-09-15 critical9.1 CVE-2024-45337 Applications and libraries which misuse connection.serverAuthenticate (via callback field ServerConfig.PublicKeyCallback) may be susceptible to an authorizatio… go · golang.org/x/crypto 2024-12-11 critical9.8 CVE-2024-52009 Atlantis is a self-hosted golang application that listens for Terraform pull request events via webhooks. go · github.com/runatlantis/atlantis 2024-11-08 critical9.8 CVE-2024-24790 The various Is methods (IsPrivate, IsLoopback, etc) did not work as expected for IPv4-mapped IPv6 addresses, returning false for addresses which would return t… golang · go 2024-06-05 critical9.8 CVE-2023-39320 The go.mod toolchain directive, introduced in Go 1.21, can be leveraged to execute scripts and binaries relative to the root of the module when the "go" comman… golang · go 2023-09-08 critical9.8 CVE-2023-29405 The go command may execute arbitrary code at build time when using cgo. golang · go, fedoraproject · fedora 2023-06-08 critical9.8 CVE-2023-29404 The go command may execute arbitrary code at build time when using cgo. golang · go, fedoraproject · fedora 2023-06-08 critical9.8 CVE-2023-29402 The go command may generate unexpected code at build time when using cgo. golang · go, fedoraproject · fedora 2023-06-08 critical9.8 CVE-2023-24540 Not all valid JavaScript whitespace characters are considered to be whitespace. golang · go 2023-05-11 critical9.8 CVE-2023-24538 Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected. golang · go 2023-04-06 critical9.1 CVE-2020-36569 golang-nanoauth authentication bypass vulnerability go · github.com/nanobox-io/golang-nanoauth 2022-12-27 critical9.6 CVE-2022-39395 Vela is a Pipeline Automation (CI/CD) framework built on Linux container technology written in Golang. go · github.com/go-vela/server, go · github.com/go-vela/worker 2022-11-09 critical9.1 CVE-2022-23806 Curve.IsOnCurve in crypto/elliptic in Go before 1.16.14 and 1.17.x before 1.17.7 can incorrectly return true in situations with a big.Int value that is not a v… golang · go, netapp · beegfs_csi_driver, netapp · cloud_insights_telegraf_agent +3 2022-02-11 critical9.8 CVE-2021-38297 Go before 1.16.9 and 1.17.x before 1.17.2 has a Buffer Overflow via large arguments in a function invocation from a WASM module, when GOARCH=wasm GOOS=js is us… golang · go, fedoraproject · fedora 2021-10-18 critical9.8 CVE-2012-2666 golang/go in 1.0.2 fixes all.bash on shared machines. golang · go 2021-07-09 critical9.8 CVE-2020-29511 The encoding/xml package in Go (all versions) does not correctly preserve the semantics of element namespace prefixes during tokenization round-trips, which al… golang · go, netapp · trident 2020-12-14 critical9.8 CVE-2020-29510 The encoding/xml package in Go versions 1.15 and earlier does not correctly preserve the semantics of directives during tokenization round-trips, which allows … golang · go, netapp · trident 2020-12-14

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.