NetSight

Security Dashboard

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

Reset
331 matching advisories · page 2 of 12Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
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 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 medium5.3 CVE-2026-39835 SSH servers which use CertChecker as a public key callback without setting IsUserAuthority or IsHostAuthority could be caused to panic by a client presenting a… 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 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 medium6.3 CVE-2026-39828 When an SSH server authentication callback returned PartialSuccessError with non-nil Permissions, those permissions were silently discarded, potentially droppi… go · golang.org/x/crypto 2026-05-22 medium6.5 CVE-2026-39827 An authenticated SSH client that repeatedly opened channels which were rejected by the server caused unbounded memory growth, eventually crashing the server pr… go · golang.org/x/crypto 2026-05-22 medium4.1 GHSA-pmwq-pjrm-6p5r in-toto-golang and in-toto-python have inconsistent negation behavior go · github.com/in-toto/in-toto-golang 2026-05-08 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 medium6.1 CVE-2026-39826 If a trusted template author were to write a <script> tag containing an empty 'type' attribute or a 'type' attribute with an ASCII whitespace, the execution of… golang · go 2026-05-07 medium5.3 CVE-2026-39825 ReverseProxy can forward queries containing parameters not visible to Rewrite functions. golang · go 2026-05-07 medium6.1 CVE-2026-39823 CVE-2026-27142 fixed a vulnerability in which URLs were not correctly escaped inside of a <meta> tag's <content> attribute. 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 medium5.3 CVE-2026-39819 The "go bug" command writes to two files with predictable names in the system temporary directory... golang · go 2026-05-07 medium5.9 CVE-2026-39817 The "go tool pack" subcommand (usually used only by the compiler as an internal tool with known... 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 medium6.8 CVE-2026-6863 Velociraptor versions prior to 0.76.4 contain a cross organization authorization bypass in the HTTP API. go · www.velocidex.com/golang/velociraptor 2026-05-06 medium5.0 CVE-2026-7573 An authorization bypass (CWE-639) in the GetUserRoles gRPC API endpoint in Velocidex Velociraptor below version 0.76.5 allows any authenticated low-privilege u… go · www.velocidex.com/golang/velociraptor 2026-05-06 medium4.4 CVE-2026-7572 An off-by-one error (CWE-193) in the ConsumeUnit16Array and ConsumeUnit64Array functions in Velocidex Velociraptor before version 0.76.5 on Windows and Linux a… go · www.velocidex.com/golang/velociraptor 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 medium6.1 CVE-2026-33812 Parsing a malicious font file can cause excessive memory allocation. golang · image 2026-04-21

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.