NetSight

Security Dashboard

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

Reset
60 matching advisories · page 2 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.1 CVE-2026-123519 Vikunja before 2.7.1 contains a denial of service vulnerability that allows authenticated users to exhaust API process memory by uploading WeKan or vikunja-fil… go-vikunja · vikunja 14 days ago medium5.3 CVE-2026-123518 Vikunja before 2.7.1 contains an incorrect authorization vulnerability in TaskBucket.CanUpdate, which checks write access to the bucket's project and to the ta… go-vikunja · vikunja 14 days ago high7.1 CVE-2026-123517 Vikunja before 2.7.1 contains an information disclosure vulnerability that allows authenticated users to determine whether private teams exist by calling the t… go-vikunja · vikunja 14 days ago high7.1 CVE-2026-123516 Vikunja before 2.7.1 contains a resource exhaustion vulnerability in the vikunja-file ZIP importer that allows authenticated users to consume CPU and memory by… go-vikunja · vikunja 14 days ago medium5.1 CVE-2026-123515 Vikunja before 2.7.1 contains a client-side request forgery vulnerability that allows users with write access to make viewers' clients request loopback or LAN … go-vikunja · vikunja 14 days ago medium5.3 CVE-2026-123514 Vikunja before 2.7.1 contains an improper resource cleanup vulnerability that leaves full-data export archives orphaned on disk after re-exports, failed export… go-vikunja · vikunja 14 days ago high7.6 CVE-2026-123513 Vikunja before 2.7.1 contains a credential exposure vulnerability that allows attackers to steal stored auth tokens by inducing users to switch the frontend AP… go-vikunja · vikunja 14 days ago high8.4 CVE-2026-123512 Vikunja before 2.7.1 embeds live password-reset, email-confirmation and account-deletion tokens in the URL query string of emailed links, so the full request U… go-vikunja · vikunja 14 days ago medium5.3 CVE-2026-123511 Vikunja before 2.7.1 contains an uncontrolled resource consumption vulnerability that allows authenticated CalDAV clients to create unbounded dummy tasks by se… go-vikunja · vikunja 14 days ago low1.0 CVE-2026-123510 Vikunja before 2.7.1 fails to re-anchor PluginsDir and LogPath to service.rootpath, allowing plugins to load from and logs to be written in the startup working… go-vikunja · vikunja 14 days ago medium4.3 CVE-2026-123509 Vikunja before 2.7.1 contains an uncontrolled resource consumption vulnerability that allows project writers or view admins to create unlimited kanban buckets … go-vikunja · vikunja 14 days ago low2.0 CVE-2026-123508 Vikunja before 2.7.1 contains a supply chain vulnerability in its mage release targets that fetch the xgo module and Docker image by mutable latest references. go-vikunja · vikunja 14 days ago medium5.3 CVE-2026-123506 Vikunja from 2.2.0 before 2.7.1 contains an authorization bypass vulnerability that allows holders of tokens scoped only to projects_webhooks to manage the own… go-vikunja · vikunja 14 days ago medium5.1 CVE-2026-123507 Vikunja from 0.24.0 before 2.7.1 contains a nil pointer dereference vulnerability that allows project admins to break project views by saving a filter-mode buc… go-vikunja · vikunja 14 days ago medium5.5 CVE-2026-123505 Vikunja before 2.7.1 contains an insecure file permissions vulnerability that allows local users to read stored data because localStorage.Write creates blobs w… go-vikunja · vikunja 14 days ago medium5.3 CVE-2026-123503 Vikunja before 2.7.1 contains an improper authorization vulnerability in canDoBucket that allows users with project write access to delete buckets via a mismat… go-vikunja · vikunja 14 days ago medium5.3 CVE-2026-123504 Vikunja from 0.22.0 before 2.7.1 contains an information disclosure vulnerability that allows read-only project members to view full webhook target URLs by lis… go-vikunja · vikunja 14 days ago medium6.9 CVE-2026-123502 Vikunja before 2.7.1 contains an information exposure vulnerability that allows log readers to obtain link-share hashes because the request logger records the … go-vikunja · vikunja 14 days ago high7.1 CVE-2026-123501 Vikunja before 2.7.1 contains an uncontrolled resource consumption vulnerability that allows authenticated users to exhaust server memory through concurrent im… go-vikunja · vikunja 14 days ago medium6.0 CVE-2026-123499 Vikunja veans before 2.7.1 contains a credential exposure vulnerability that allows malicious repository authors to capture API tokens by specifying an attacke… go-vikunja · vikunja 14 days ago medium6.9 CVE-2026-123500 Vikunja before 2.7.1 contains an insecure file permissions vulnerability that allows local users to read dump archives created with umask permissions by the vi… go-vikunja · vikunja 14 days ago low2.1 CVE-2026-123498 Vikunja veans before 2.7.1 contains a prompt injection vulnerability that allows project members with write access to inject instructions by setting project ti… go-vikunja · vikunja 14 days ago high7.6 CVE-2026-123497 Vikunja veans before 2.7.1 contains a protocol downgrade vulnerability in serverCandidates that allows on-path attackers to force plain HTTP during veans init … go-vikunja · vikunja 14 days ago medium4.8 CVE-2026-123496 Vikunja veans before 2.7.1 contains a symlink following vulnerability that allows attackers to make veans init write files outside the repository via crafted r… go-vikunja · vikunja 14 days ago medium5.1 CVE-2026-123495 Vikunja 2.0.0 before 2.7.1 accepts form-encoded bodies on the /api/v2 login and OIDC callback endpoints without CSRF or Origin checks, enabling login cross-sit… go-vikunja · vikunja 14 days ago medium5.1 CVE-2026-123494 Vikunja before 2.7.1 contains a cross-site request forgery vulnerability that allows attackers to import their data into a victim's account because the Todoist… go-vikunja · vikunja 14 days ago medium5.4 CVE-2026-123493 Vikunja from 2.4.0 before 2.7.1 contains an authentication bypass vulnerability that allows disabled or locked users to retain access through API tokens owned … go-vikunja · vikunja 14 days ago high7.5 GHSA-m4vj-wr5q-cmvr Duplicate Advisory: Vikunja: Every /api/v2 pre-auth endpoint is unthrottled on a stock install while its /api/v1 twin is rate limited go · github.com/go-vikunja/vikunja 2026-09-15 high6.5 GHSA-p4h8-xg7f-xqrc Duplicate Advisory: Vikunja: Denial of service via decompression bomb in the data import go · github.com/go-vikunja/vikunja 2026-09-15 high7.7 CVE-2026-76216 Vikunja before 2.5.0 contains a principal-type confusion vulnerability where LinkSharing principals with id N are treated as user principals with users.id == N… go · code.vikunja.io/api 2026-08-19

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.