NetSight

Security Dashboard

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

Reset
134 matching advisories · page 1 of 5Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.1 CVE-2026-109357 LibreNMS before 26.9.0 contains an LDAP filter injection in ldap-authorization and ad-authorization modes because usernames are inserted unescaped into LDAP se… LibreNMS 40 days ago medium4.3 CVE-2026-109356 LibreNMS before 26.9.0 contains a missing authorization vulnerability in PortsController::purge that allows global-read users to physically delete ports withou… LibreNMS 40 days ago medium6.1 CVE-2026-109355 LibreNMS before 26.9.0 contains a stored cross-site scripting vulnerability in get_oxidized_nodes_list() that renders Oxidized API fields and SNMP sysName unes… LibreNMS 40 days ago medium4.3 CVE-2026-109354 LibreNMS before 26.9.0 contains a path traversal vulnerability in nfsen_channel_common.inc.php that allows authenticated users to read unauthorized RRD data by… LibreNMS 40 days ago high7.1 CVE-2026-109353 LibreNMS before 26.9.0 contains an SQL injection vulnerability that allows unprivileged users to inject SQL by supplying an array-valued notification_id parame… LibreNMS 40 days ago medium6.1 CVE-2026-109352 LibreNMS before 26.9.0 contains a stored cross-site scripting vulnerability in includes/html/pages/device/wireless.inc.php, which echoes wireless sensor sensor… LibreNMS 40 days ago medium4.3 CVE-2026-108715 LibreNMS through 26.9.1.1 contains an authorization bypass vulnerability in includes/html/graphs/smokeping/auth.inc.php that checks the src probe device instea… LibreNMS 41 days ago medium5.0 CVE-2020-15875 An issue was discovered in LibreNMS 1.65. 2026-09-13 high8.8 CVE-2026-86427 LibreNMS before 26.8.0 contains an argument injection vulnerability in the graph_title parameter that allows authenticated attackers to inject arbitrary rrdtoo… librenms · librenms 2026-09-07 critical9.8 CVE-2026-86426 LibreNMS before 26.8.0 contains an authentication bypass vulnerability in the REST API that allows unauthenticated attackers to access protected endpoints by s… librenms · librenms 2026-09-07 high8.6 CVE-2026-84194 LibreNMS versions >= 23.10.0 and < 26.2.0 (fixed in 26.4.0) contain an authenticated OS command injection vulnerability in libvirt discovery. LibreNMS versions >= 23.10.0 and 2026-09-01 medium5.8 CVE-2026-84193 LibreNMS through 26.2.0 contains a stored cross-site scripting vulnerability in legacy PHP template pages that render unescaped SNMP-sourced data fields includ… LibreNMS 2026-09-01 high7.1 CVE-2026-84192 LibreNMS before 26.3.1 contains a stored cross-site scripting vulnerability in legacy PHP templates that output SNMP-sourced and syslog-sourced data without es… LibreNMS 2026-09-01 medium6.1 CVE-2026-84191 LibreNMS before 26.5.0 contains stored cross-site scripting vulnerabilities in VRF display pages where mplsVpnVrfDescription, vrf_name, and mplsVpnVrfRouteDist… LibreNMS 2026-09-01 high7.2 CVE-2026-84190 LibreNMS versions before 26.5.0 contain a remote code execution vulnerability in the AboutController where the snmpget configuration parameter is passed to she… LibreNMS 2026-09-01 high8.1 CVE-2026-84189 LibreNMS through 26.4.0 renders JSON fields (name, ip, model, author, commit message) returned by the admin-configurable Oxidized integration URL (oxidized.url… LibreNMS 2026-09-01 medium4.8 CVE-2026-84188 LibreNMS versions <= 26.4.0 contain a stored cross-site scripting vulnerability in the graph_descr.<graphtype> configuration settings, which are echoed verbati… LibreNMS 2026-09-01 high7.1 GHSA-7w8c-qgxg-m7jx LibreNMS — Stored XSS via SNMP/Syslog Data in Legacy Templates composer · librenms/librenms 2026-08-26 high8.8 CVE-2020-15878 An issue was discovered in LibreNMS 1.65. 2026-08-26 high8.8 CVE-2020-15876 An issue was discovered in LibreNMS 1.65. 2026-08-26 high8.8 CVE-2020-15874 An issue was discovered in LibreNMS 1.65. 2026-08-26 high8.6 CVE-2026-80214 LibreNMS’s Virtualization Discovery module is vulnerable to command line injection. 2026-08-26 high8.1 GHSA-7gww-x7fh-jf9j LibreNMS: SSRF-driven stored XSS via Oxidized API response fields in device showconfig page composer · librenms/librenms 2026-08-18 medium4.8 GHSA-7cj5-v4pp-v632 LibreNMS: Stored XSS via graph_descr admin config settings echoed without escaping to all authenticated users composer · librenms/librenms 2026-08-18 medium6.4 GHSA-jf24-8g2h-2wg7 LibreNMS Vulnerable to Remote Code Execution via AboutController composer · librenms/librenms 2026-08-18 high8.6 CVE-2026-55182 LibreNMS Vulnerable to Remote Code Execution by Signal Alert Transportation module composer · librenms/librenms 2026-08-18 medium5.4 CVE-2026-45694 LibreNMS: Reflected XSS via Proxmox instance/vmid GET parameters injected into document.title JavaScript assignment composer · librenms/librenms 2026-08-12 medium6.5 CVE-2026-30480 A Local File Inclusion (LFI) vulnerability in the NFSen module (nfsen.inc.php) of LibreNMS 22.11.0-23-gd091788f2 allows authenticated attackers to include arbi… 2026-04-14 high8.5 GHSA-7549-ggpq-22w8 Duplicate Advisory: LibreNMS is Vulnerable to Remote Code Execution by Arbitrary File Write composer · librenms/librenms 2026-04-13 medium4.8 GHSA-rp7w-624x-95qv Duplicate Advisory: LibreNMS affected by an authenticated Cross-site Scripting vulnerability on the showconfig page composer · librenms/librenms 2026-04-13

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.