NetSight

Security Dashboard

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

Reset
84 matching advisories · page 2 of 3Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.0 CVE-2024-6581 Lollms vulnerable to Cross-site Scripting pip · lollms 2024-10-29 high7.1 CVE-2024-6959 A vulnerability in parisneo/lollms-webui version 9.8 allows for a Denial of Service (DOS) attack when uploading an audio file. lollms · lollms_web_ui 2024-10-13 medium4.4 CVE-2024-6985 Lord of Large Language Models (LoLLMs) path traversal vulnerability in the api open_personality_folder endpoint pip · lollms 2024-10-11 medium4.4 CVE-2024-6971 Lord of Large Language Models (LoLLMs) Server path traversal vulnerability in lollms_file_system.py pip · lollms 2024-10-11 high7.5 CVE-2024-6394 A Local File Inclusion vulnerability exists in parisneo/lollms-webui versions below v9.8. lollms · lollms_web_ui 2024-09-30 high8.8 CVE-2024-6040 In parisneo/lollms-webui version v9.8, the lollms_binding_infos is missing the client_id parameter, which leads to multiple security vulnerabilities. lollms · lollms_web_ui 2024-08-01 high7.3 CVE-2024-6281 LoLLMS vulnerable to Expected Behavior Violation pip · lollms 2024-07-20 high8.4 CVE-2024-4897 parisneo/lollms-webui, in its latest version, is vulnerable to remote code execution due to an insecure dependency on llama-cpp-python version llama_cpp_python… lollms · lollms_web_ui 2024-07-02 high7.5 CVE-2024-6250 An absolute path traversal vulnerability exists in parisneo/lollms-webui v9.6, specifically in the `open_file` endpoint of `lollms_advanced.py`. lollms · lollms_web_ui 2024-06-27 high7.3 CVE-2024-6139 lollms vulnerable to dot-dot-slash path traversal in XTTS server pip · lollms 2024-06-27 high8.6 CVE-2024-6085 lollms vulnerable to path traversal due to unauthenticated root folder settings change pip · lollms 2024-06-27 medium5.4 CVE-2024-5933 A Cross-site Scripting (XSS) vulnerability exists in the chat functionality of parisneo/lollms-webui in the latest version. lollms · lollms_web_ui 2024-06-27 high7.4 CVE-2024-5824 lollms path traversal vulnerability allows overriding of config.yaml file, leading to RCE pip · lollms 2024-06-27 high7.7 CVE-2024-4498 A Path Traversal and Remote File Inclusion (RFI) vulnerability exists in the parisneo/lollms-webui application, affecting versions v9.7 to the latest. lollms · lollms_web_ui 2024-06-25 low3.3 CVE-2024-4839 A Cross-Site Request Forgery (CSRF) vulnerability exists in the 'Servers Configurations' function of the parisneo/lollms-webui, versions 9.6 to the latest. lollms · lollms-webui 2024-06-24 medium6.3 CVE-2024-4499 A Cross-Site Request Forgery (CSRF) vulnerability exists in the XTTS server of parisneo/lollms version 9.6 due to a lax CORS policy. lollms · lollms 2024-06-24 medium6.8 CVE-2024-3121 Remote Code Execution in create_conda_env function in lollms pip · lollms 2024-06-24 low3.3 CVE-2024-4841 A Path Traversal vulnerability exists in the parisneo/lollms-webui, specifically within the 'add_reference_to_local_mode' function due to the lack of input san… lollms · lollms-webui 2024-06-23 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 high8.8 CVE-2024-4403 A Cross-Site Request Forgery (CSRF) vulnerability exists in the restart_program function of the parisneo/lollms-webui v9.6. lollms · lollms-webui 2024-06-10 high8.1 CVE-2024-4328 A Cross-Site Request Forgery (CSRF) vulnerability exists in the clear_personality_files_list function of the parisneo/lollms-webui v9.6. parisneo · lollms_web_ui 2024-06-10 high7.5 CVE-2024-4881 LoLLMS Path Traversal vulnerability pip · lollms 2024-06-06 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 high7.5 CVE-2024-2548 A path traversal vulnerability exists in the parisneo/lollms-webui application, specifically within the `lollms_core/lollms/server/endpoints/lollms_binding_fil… 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

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.