NetSight

Security Dashboard

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

Reset
39 matching advisories · page 1 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2026-30847 Wekan is an open source kanban tool built with Meteor. wekan_project · wekan 2026-03-06 high7.5 CVE-2026-30846 Wekan is an open source kanban tool built with Meteor. wekan_project · wekan 2026-03-06 high8.2 CVE-2026-30845 Wekan is an open source kanban tool built with Meteor. wekan_project · wekan 2026-03-06 high8.1 CVE-2026-30844 Wekan is an open source kanban tool built with Meteor. wekan_project · wekan 2026-03-06 medium6.5 CVE-2026-30843 Wekan is an open source kanban tool built with Meteor. wekan_project · wekan 2026-03-06 medium6.3 CVE-2026-2209 A vulnerability was detected in WeKan up to 8.18. wekan_project · wekan 2026-02-08 medium4.3 CVE-2026-2208 A security vulnerability has been detected in WeKan up to 8.20. wekan_project · wekan 2026-02-08 medium5.3 CVE-2026-2207 A weakness has been identified in WeKan up to 8.20. wekan_project · wekan 2026-02-08 medium6.3 CVE-2026-2206 A security flaw has been discovered in WeKan up to 8.20. wekan_project · wekan 2026-02-08 medium4.3 CVE-2026-2205 A vulnerability was identified in WeKan up to 8.20. wekan_project · wekan 2026-02-08 high8.8 CVE-2026-25859 Wekan versions prior to 8.20 allow non-administrative users to access migration functionality due to insufficient permission checks, potentially resulting in u… wekan_project · wekan 2026-02-07 medium4.3 CVE-2026-25568 WeKan versions prior to 8.19 contain an authorization logic vulnerability where the instance configuration setting allowPrivateOnly is not sufficiently enforce… wekan_project · wekan 2026-02-07 medium4.3 CVE-2026-25567 WeKan versions prior to 8.19 contain an insecure direct object reference (IDOR) in the card comment creation API. wekan_project · wekan 2026-02-07 medium5.4 CVE-2026-25566 WeKan versions prior to 8.19 contain an authorization vulnerability in card move logic. wekan_project · wekan 2026-02-07 medium6.5 CVE-2026-25565 WeKan versions prior to 8.19 contain an authorization vulnerability where certain card update API paths validate only board read access rather than requiring w… wekan_project · wekan 2026-02-07 high7.5 CVE-2026-25564 WeKan versions prior to 8.19 contain an insecure direct object reference (IDOR) in checklist creation and related checklist routes. wekan_project · wekan 2026-02-07 high7.5 CVE-2026-25563 WeKan versions prior to 8.19 contain an insecure direct object reference (IDOR) in checklist creation and related checklist routes. wekan_project · wekan 2026-02-07 medium4.3 CVE-2026-25562 WeKan versions prior to 8.19 contain an information disclosure vulnerability in the attachments publication. wekan_project · wekan 2026-02-07 high7.5 CVE-2026-25561 WeKan versions prior to 8.19 contain an authorization weakness in the attachment upload API. wekan_project · wekan 2026-02-07 critical9.8 CVE-2026-25560 WeKan versions prior to 8.19 contain an LDAP filter injection vulnerability in LDAP authentication. wekan_project · wekan 2026-02-07 medium4.3 CVE-2026-1964 A vulnerability was determined in WeKan up to 8.20. wekan_project · wekan 2026-02-05 medium6.3 CVE-2026-1963 A vulnerability was found in WeKan up to 8.20. wekan_project · wekan 2026-02-05 medium6.3 CVE-2026-1962 A vulnerability has been found in WeKan up to 8.20. wekan_project · wekan 2026-02-05 medium6.3 CVE-2026-1898 A vulnerability was determined in WeKan up to 8.20. wekan_project · wekan 2026-02-05 medium4.3 CVE-2026-1897 A vulnerability was found in WeKan up to 8.20. wekan_project · wekan 2026-02-05 medium6.3 CVE-2026-1896 A vulnerability has been found in WeKan up to 8.20. wekan_project · wekan 2026-02-05 medium6.3 CVE-2026-1895 A flaw has been found in WeKan up to 8.20. wekan_project · wekan 2026-02-04 medium6.3 CVE-2026-1894 A vulnerability was detected in WeKan up to 8.20. wekan_project · wekan 2026-02-04 medium5.0 CVE-2026-1892 A security vulnerability has been detected in WeKan up to 8.20. wekan_project · wekan 2026-02-04 medium6.5 CVE-2025-65782 An issue was discovered in Wekan The Open Source kanban board system up to version 18.15, fixed in 18.16. wekan_project · wekan 2025-12-15

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.