NetSight

Security Dashboard

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

Reset
79 matching advisories · page 2 of 3Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2026-32815 SiYuan Vulnerable to Cross-Origin WebSocket Hijacking via Authentication Bypass — Unauthenticated Information Disclosure go · github.com/siyuan-note/siyuan/kernel 2026-03-16 medium6.8 CVE-2026-32747 SiYuan globalCopyFiles: incomplete sensitive path blocklist allows reading /proc and Docker secrets go · github.com/siyuan-note/siyuan/kernel 2026-03-16 medium6.5 CVE-2026-32704 SiYuan's renderSprig has a missing admin check that allows any user to read full workspace DB go · github.com/siyuan-note/siyuan/kernel 2026-03-13 high8.3 CVE-2026-32110 SiYuan has a Full-Read SSRF via /api/network/forwardProxy go · github.com/siyuan-note/siyuan/kernel 2026-03-11 medium6.4 CVE-2026-31809 SiYuan has a SVG Sanitizer Bypass via Whitespace in `javascript:` URI — Unauthenticated XSS go · github.com/siyuan-note/siyuan/kernel 2026-03-10 medium6.4 CVE-2026-31807 SiYuan has a SVG Sanitizer Bypass via `<animate>` Element — Unauthenticated XSS go · github.com/siyuan-note/siyuan/kernel 2026-03-10 high7.1 CVE-2026-30926 SiYuan: Authorization Bypass Allows Low-Privilege Publish User to Modify Notebook Content via /api/block/appendHeadingChildren go · github.com/siyuan-note/siyuan/kernel 2026-03-09 critical9.3 CVE-2026-30869 SiYuan Vulnerable to Path Traversal in /export Endpoint Allows Arbitrary File Read and Secret Leakage go · github.com/siyuan-note/siyuan/kernel 2026-03-07 critical9.3 CVE-2026-29183 SiYuan: Unauthenticated Reflected XSS via SVG Injection in /api/icon/getDynamicIcon Endpoint go · github.com/siyuan-note/siyuan/kernel 2026-03-04 high8.8 CVE-2026-29073 SiYuan's direct SQL Query API accessible to Reader-level users enables unauthorized database access go · github.com/siyuan-note/siyuan/kernel 2026-03-03 medium4.6 CVE-2026-25647 Lute is a structured Markdown engine supporting Go and JavaScript. b3log · siyuan 2026-02-06 critical9.1 CVE-2026-25539 SiYuan has Arbitrary File Write via /api/file/copyFile leading to RCE go · github.com/siyuan-note/siyuan/kernel 2026-01-29 high7.5 CVE-2026-25992 SiYuan File Read API Case Sensitivity Bypass can Lead to Path Traversal go · github.com/siyuan-note/siyuan/kernel 2026-01-28 critical9.6 CVE-2026-23852 SiYuan is a personal knowledge management system. b3log · siyuan 2026-01-19 high8.3 CVE-2026-23851 SiYuan Vulnerable to Arbitrary File Read via File Copy Functionality go · github.com/siyuan-note/siyuan/kernel 2026-01-19 high7.8 CVE-2026-23850 SiYuan vulnerable to Arbitrary file Read / SSRF go · github.com/siyuan-note/siyuan/kernel 2026-01-19 medium6.1 CVE-2026-23847 SiYuan has a Reflected Cross-Site Scripting (XSS) via /api/icon/getDynamicIcon go · github.com/siyuan-note/siyuan/kernel 2026-01-19 medium5.3 CVE-2026-23645 SiYuan Has a Stored Cross-Site Scripting (XSS) Vulnerability via Unrestricted SVG File Upload go · github.com/siyuan-note/siyuan/kernel 2026-01-16 high8.1 CVE-2025-68948 SiYuan is self-hosted, open source personal knowledge management software. b3log · siyuan 2025-12-27 high7.8 CVE-2025-67488 SiYuan: ZipSlip -> Arbitrary File Overwrite -> RCE go · github.com/siyuan-note/siyuan/kernel 2025-12-09 critical9.1 CVE-2025-21609 SiYuan has an arbitrary file deletion vulnerability go · github.com/siyuan-note/siyuan/kernel 2025-01-03 high7.5 CVE-2024-55657 SiYuan has an arbitrary file read via /api/template/render go · github.com/siyuan-note/siyuan/kernel 2024-12-11 high7.5 CVE-2024-55658 SiYuan has an arbitrary file read and path traversal via /api/export/exportResources go · github.com/siyuan-note/siyuan/kernel 2024-12-11 high8.7 CVE-2024-55659 SiYuan has an arbitrary file write in the host via /api/asset/upload go · github.com/siyuan-note/siyuan/kernel 2024-12-11 critical9.8 CVE-2024-55660 SiYuan has an SSTI via /api/template/renderSprig go · github.com/siyuan-note/siyuan/kernel 2024-12-11 critical9.8 CVE-2024-53507 A SQL injection vulnerability was discovered in Siyuan 3.1.11 in /getHistoryItems. b3log · siyuan 2024-11-29 critical9.8 CVE-2024-53506 A SQL injection vulnerability has been identified in Siyuan 3.1.11 via the ids array parameter in /batchGetBlockAttrs. b3log · siyuan 2024-11-29 critical9.8 CVE-2024-53505 A SQL injection vulnerability has been identified in Siyuan 3.1.11 via the id parameter at /getAssetContent. b3log · siyuan 2024-11-29 critical9.8 CVE-2024-53504 A SQL injection vulnerability has been identified in Siyuan 3.1.11 via the notebook parameter in /searchHistory. b3log · siyuan 2024-11-29 low3.5 CVE-2024-6938 A vulnerability has been found in SiYuan 3.1.0 and classified as problematic. b3log · siyuan 2024-07-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.