NetSight

Security Dashboard

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

Reset
29 matching advisories · page 1 of 1Index updated 10 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.6 CVE-2026-1115 A Stored Cross-Site Scripting (XSS) vulnerability was identified in the social feature of parisneo/lollms, affecting the latest version prior to 2.2.0. pip · lollms 2026-04-10 critical9.8 CVE-2026-1114 In parisneo/lollms version 2.1.0, the application's session management is vulnerable to improper access control due to the use of a weak secret key for signing… pip · lollms 2026-04-07 critical9.8 CVE-2026-0558 A vulnerability in parisneo/lollms, up to and including version 2.2.0, allows unauthenticated users to upload and process files through the `/api/files/extract… lollms · lollms 2026-03-29 critical9.1 CVE-2026-33340 LoLLMs WEBUI provides the Web user interface for Lord of Large Language and Multi modal Systems. lollms · lollms_web_ui 2026-03-24 critical9.6 CVE-2024-2356 A Local File Inclusion (LFI) vulnerability exists in the '/reinstall_extension' endpoint of the parisneo/lollms-webui application, specifically within the `nam… 2026-02-02 critical9.8 CVE-2024-8898 A path traversal vulnerability exists in the `install` and `uninstall` API endpoints of parisneo/lollms-webui version V12 (Strawberry). lollms · lollms_web_ui 2025-03-20 critical9.1 CVE-2024-8581 A vulnerability in the `upload_app` function of parisneo/lollms-webui V12 (Strawberry) allows an attacker to delete any file or directory on the system. lollms · lollms_web_ui 2025-03-20 critical9.0 CVE-2024-6581 Lollms vulnerable to Cross-site Scripting pip · lollms 2024-10-29 critical9.8 CVE-2024-5443 Remote Code Execution via path traversal bypass in lollms pip · lollms 2024-06-22 critical9.1 CVE-2024-4315 parisneo/lollms Local File Inclusion (LFI) attack pip · lollms 2024-06-12 critical9.8 CVE-2024-4320 A remote code execution (RCE) vulnerability exists in the '/install_extension' endpoint of the parisneo/lollms-webui application, specifically within the `@rou… lollms · lollms_web_ui 2024-06-06 critical9.8 CVE-2024-3429 LoLLMS Path Traversal vulnerability pip · lollms 2024-06-06 critical9.8 CVE-2024-3322 A path traversal vulnerability exists in the 'cyber_security/codeguard' native personality of the parisneo/lollms-webui, affecting versions up to 9.5. lollms · lollms_web_ui 2024-06-06 critical9.8 CVE-2024-2624 A path traversal and arbitrary file upload vulnerability exists in the parisneo/lollms-webui application, specifically within the `@router.get("/switch_persona… lollms · lollms_web_ui 2024-06-06 critical9.1 CVE-2024-2362 A path traversal vulnerability exists in the parisneo/lollms-webui version 9.3 on the Windows platform. lollms · lollms_web_ui 2024-06-06 critical9.8 CVE-2024-2360 parisneo/lollms-webui is vulnerable to path traversal attacks that can lead to remote code execution due to insufficient sanitization of user-supplied input in… lollms · lollms_web_ui 2024-06-06 critical9.8 CVE-2024-2359 A vulnerability in the parisneo/lollms-webui version 9.3 allows attackers to bypass intended access restrictions and execute arbitrary code. lollms · lollms_web_ui 2024-06-06 critical9.1 CVE-2024-1873 parisneo/lollms-webui is vulnerable to path traversal and denial of service attacks due to an exposed `/select_database` endpoint in version a9d16b0. lollms · lollms_web_ui 2024-06-06 critical9.8 CVE-2024-5482 A Server-Side Request Forgery (SSRF) vulnerability exists in the 'add_webpage' endpoint of the parisneo/lollms-webui application, affecting the latest version. lollms · lollms_web_ui 2024-06-06 critical9.8 CVE-2024-4267 A remote code execution (RCE) vulnerability exists in the parisneo/lollms-webui, specifically within the 'open_file' module, version 9.5. lollms · lollms-webui 2024-05-22 critical9.8 CVE-2024-4326 A vulnerability in parisneo/lollms-webui versions up to 9.3 allows remote attackers to execute arbitrary code. lollms · lollms_web_ui 2024-05-16 critical9.8 CVE-2024-4078 LoLLMS Command Injection vulnerability pip · lollms 2024-05-16 critical9.0 CVE-2024-2366 A remote code execution vulnerability exists in the parisneo/lollms-webui application, specifically within the reinstall_binding functionality in lollms_core/l… lollms · lollms_web_ui 2024-05-16 critical9.6 CVE-2024-2361 A vulnerability in the parisneo/lollms-webui allows for arbitrary file upload and read due to insufficient sanitization of user-supplied input. lollms · lollms_web_ui 2024-05-16 critical9.8 CVE-2024-2358 A path traversal vulnerability in the '/apply_settings' endpoint of parisneo/lollms-webui allows attackers to execute arbitrary code. lollms · lollms_web_ui 2024-05-16 critical9.8 CVE-2024-1601 An SQL injection vulnerability exists in the `delete_discussion()` function of the parisneo/lollms-webui application, allowing an attacker to delete all discus… lollms · lollms-webui 2024-04-16 critical9.3 CVE-2024-1600 A Local File Inclusion (LFI) vulnerability exists in the parisneo/lollms-webui application, specifically within the `/personalities` route. lollms · lollms_web_ui 2024-04-10 critical9.8 CVE-2024-1520 An OS Command Injection vulnerability exists in the '/open_code_folder' endpoint of the parisneo/lollms-webui application, due to improper validation of user-s… lollms · lollms_web_ui 2024-04-10 critical9.8 CVE-2024-1511 The parisneo/lollms-webui repository is susceptible to a path traversal vulnerability due to inadequate validation of user-supplied file paths. lollms · lollms_web_ui 2024-04-10

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.