NetSight

Security Dashboard

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

Reset
52 matching advisories · page 1 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.1 CVE-2026-30586 Cross Site Scripting vulnerability in usememos Memos v.0.26.0 allows a remote attacker to obtain sensitive information via the SANITIZE_SCHEMA, Memo Rendering … 2026-06-02 medium6.3 CVE-2026-6634 A weakness has been identified in usememos memos up to 0.22.1. go · github.com/usememos/memos 2026-04-20 medium4.3 CVE-2025-65799 memos lacks file name validation or verification go · github.com/usememos/memos 2025-12-08 medium6.5 CVE-2025-65797 memos vulnerability allows arbitrarily modification or deletion registered identity providers go · github.com/usememos/memos 2025-12-08 medium5.4 CVE-2025-65798 memos vulnerability allows arbitrarily modification or deletion of attachments go · github.com/usememos/memos 2025-12-08 medium4.3 CVE-2025-65796 memos vulnerability allows arbitrarily reactions deletion go · github.com/usememos/memos 2025-12-08 medium5.4 CVE-2025-56761 Memos 0.22 is vulnerable to Stored Cross site scripting (XSS) vulnerabilities by the upload attachment and user avatar features. go · github.com/usememos/memos 2025-09-03 medium4.3 CVE-2025-56760 When Memos 0.22 is configured to store objects locally, an attacker can create a file via the CreateResource endpoint containing a path traversal sequence in t… go · github.com/usememos/memos 2025-09-03 medium5.4 CVE-2023-0109 Stored XSS using two files in usememos/memos go · github.com/usememos/memos 2024-11-15 medium6.1 CVE-2024-29029 memos vulnerable to Server-Side Request Forgery and Cross-site Scripting go · github.com/usememos/memos 2024-04-19 medium5.8 CVE-2024-29030 memos vulnerable to Server-Side Request Forgery in /api/resource go · github.com/usememos/memos 2024-04-19 medium5.8 CVE-2024-29028 memos vulnerable to Server-Side Request Forgery in /o/get/httpmeta go · github.com/usememos/memos 2024-04-19 medium6.1 CVE-2022-25978 Cross Site Scripting in usememos/memos go · github.com/usememos/memos 2023-02-15 medium5.4 CVE-2023-0112 usememos/memos vulnerable to stored Cross-site Scripting go · github.com/usememos/memos 2023-01-07 medium5.4 CVE-2023-0111 usememos/memos vulnerable to stored Cross-site Scripting go · github.com/usememos/memos 2023-01-07 medium5.4 CVE-2023-0110 usememos/memos vulnerable to stored Cross-site Scripting go · github.com/usememos/memos 2023-01-07 medium5.4 CVE-2023-0108 usememos/memos vulnerable to stored Cross-site Scripting go · github.com/usememos/memos 2023-01-07 medium5.4 CVE-2023-0107 usememos/memos vulnerable to stored Cross-site Scripting go · github.com/usememos/memos 2023-01-07 medium5.4 CVE-2023-0106 usememos/memos vulnerable to stored Cross-site Scripting go · github.com/usememos/memos 2023-01-07 medium6.5 CVE-2022-4863 usememos/memos vulnerable to Improper Handling of Insufficient Permissions or Privileges go · github.com/usememos/memos 2022-12-30 medium5.3 CVE-2022-4851 sememos/memos vulnerable to Improper Handling of Values go · github.com/usememos/memos 2022-12-29 medium6.5 CVE-2022-4850 usememos/memos Cross-Site Request Forgery vulnerability go · github.com/usememos/memos 2022-12-29 medium6.5 CVE-2022-4849 usememos/memos Cross-Site Request Forgery vulnerability go · github.com/usememos/memos 2022-12-29 medium5.7 CVE-2022-4848 usememos/memos vulnerable to Improper Verification of Source of a Communication Channel go · github.com/usememos/memos 2022-12-29 medium6.5 CVE-2022-4847 usememos/memos has Incorrectly Specified Destination in a Communication Channel go · github.com/usememos/memos 2022-12-29 medium6.5 CVE-2022-4846 usememos/memos Cross-Site Request Forgery vulnerability go · github.com/usememos/memos 2022-12-29 medium4.3 CVE-2022-4845 usememos/memos Cross-Site Request Forgery vulnerability go · github.com/usememos/memos 2022-12-29 medium5.4 CVE-2022-4841 usememos/memos vulnerable to stored Cross-site Scripting go · github.com/usememos/memos 2022-12-29 medium5.4 CVE-2022-4840 usememos/memos vulnerable to stored Cross-site Scripting go · github.com/usememos/memos 2022-12-29 medium5.4 CVE-2022-4839 usememos/memos vulnerable to stored Cross-site Scripting go · github.com/usememos/memos 2022-12-29

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.