NetSight

Security Dashboard

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

Reset
126 matching advisories · page 2 of 5Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.2 CVE-2026-102119 A path traversal weakness in an optional, non-default administrative feature allowed an authenticated administrator to move files to unintended locations outsi… accellion · kiteworks 52 days ago high7.8 CVE-2026-102118 A local privilege escalation vulnerability in Kiteworks could have allowed an attacker with an existing shell under a low-privileged service account to escalat… accellion · kiteworks 52 days ago high7.2 CVE-2026-102117 On deployments where the remote-support capability is licensed and enabled, an authenticated System Administrator who also possessed the key protecting the sub… accellion · kiteworks 52 days ago high7.2 CVE-2026-102116 -A weakness could have allowed an authenticated Kiteworks Email Protection Gateway administrator to write a file outside its intended location and cause the ap… accellion · kiteworks 52 days ago critical9.8 CVE-2026-102115 Kiteworks Core did not correctly validate a parameter submitted to the password reset workflow. accellion · kiteworks 52 days ago high7.2 CVE-2026-102114 A command injection vulnerability in Kiteworks could allow a high-privileged authenticated administrator to execute arbitrary operating-system commands as root… accellion · kiteworks 52 days ago high7.8 CVE-2026-102113 A privilege escalation vulnerability in Kiteworks could allow an attacker who has already obtained code execution as an unprivileged backend service account on… accellion · kiteworks 52 days ago high7.8 CVE-2026-102112 A privilege escalation vulnerability in Kiteworks could allow an attacker who has already obtained code execution as an unprivileged backend service account on… accellion · kiteworks 52 days ago medium4.9 CVE-2026-102111 Kiteworks did not enforce the maximum permitted value for a configurable security-policy setting. accellion · kiteworks 52 days ago medium5.9 CVE-2026-102110 An endpoint used during initial appliance setup did not require authentication and did not correctly enforce its intended state precondition, so during the ini… accellion · kiteworks 52 days ago high7.1 CVE-2026-102109 A SQL injection vulnerability existed in Kiteworks Secure Data Forms, where a value derived from the authenticated user's stored account data was incorporated … accellion · kiteworks 52 days ago high7.2 CVE-2026-102108 An authenticated administrator of Kiteworks Email Protection Gateway could submit a crafted serialized object to a cluster management interface that was deseri… accellion · kiteworks 52 days ago medium4.6 CVE-2026-102107 Kiteworks Core contains a business logic flaw in a Kiteworks file-request feature allowed an authenticated user to send a request that appeared to originate fr… accellion · kiteworks 52 days ago critical9.1 CVE-2026-102106 Improper authentication in a Kiteworks Email Protection Gateway administrative service. accellion · kiteworks 52 days ago critical9.1 CVE-2026-102105 Kiteworks Email Protection Gateway before version 9.5.0 is vulnerable to Server-Side Request Forgery (SSRF). accellion · kiteworks 52 days ago critical9.1 CVE-2026-102104 Kiteworks Email Protection Gateway before version 9.5.0 is vulnerable to Server-Side Request Forgery (SSRF). accellion · kiteworks 52 days ago critical9.1 CVE-2026-102103 Kiteworks Email Protection Gateway before version 9.5.0 is vulnerable to Server-Side Request Forgery (SSRF). accellion · kiteworks 52 days ago critical9.1 CVE-2026-102102 Kiteworks Email Protection Gateway before version 9.5.0 is vulnerable to Server-Side Request Forgery (SSRF). accellion · kiteworks 52 days ago high8.1 CVE-2026-102101 Kiteworks Core before version 9.5.0 is vulnerable to Deserialization of Untrusted Data. accellion · kiteworks 52 days ago high8.7 CVE-2026-102100 Kiteworks Core before version 9.5.0 is vulnerable to Stored Cross-Site Scripting. accellion · kiteworks 52 days ago high7.2 CVE-2026-102099 Kiteworks Core before version 9.5.0 is vulnerable to Arbitrary File Write. accellion · kiteworks 52 days ago high7.2 CVE-2026-102098 Kiteworks Core before version 9.5.0 is vulnerable to SQL Injection. accellion · kiteworks 52 days ago high7.2 CVE-2026-102097 Kiteworks Email Protection Gateway before version 9.5.0 is vulnerable to Remote Code Execution. accellion · kiteworks 52 days ago high7.2 CVE-2026-102096 Kiteworks Core before version 9.5.0 is vulnerable to OS Command Injection that allows an authenticated administrator to upload a configuration package whose co… accellion · kiteworks 52 days ago critical9.1 CVE-2026-102095 Kiteworks Email Protection Gateway before version 9.5.0 is vulnerable to Server-Side Request Forgery. accellion · kiteworks 52 days ago high7.2 CVE-2026-102094 Kiteworks Email Protection Gateway before version 9.5.0 is vulnerable to Unsafe Reflection and does not sufficiently restrict the code that the mail-processing… accellion · kiteworks 52 days ago high7.2 CVE-2026-102093 Kiteworks Core before version 9.5.0 is vulnerable to Improper Privilege Management and does not correctly enforce restrictions on role assignment, which could … accellion · kiteworks 52 days ago high8.7 CVE-2026-102092 Kiteworks Core before version 9.5.0 is vulnerable to Stored Cross-site Scripting (XSS) that could allow an authenticated user to store crafted content that exe… accellion · kiteworks 52 days ago high7.5 CVE-2026-102091 Kiteworks Secure Data Forms before version 9.5.0 is vulnerable to Server-Side Request Forgery that could allow an unauthenticated, remote attacker to make the … accellion · kiteworks 52 days ago medium4.3 CVE-2026-102090 Kiteworks Core before version 9.5.1 is vulnerable to Content Injection. accellion · kiteworks 52 days ago

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.