NetSight

Security Dashboard

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

Reset
22 matching advisories · page 1 of 1Index updated 5 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.2 CVE-2026-61552 Icinga 2 is an open source monitoring system. 2026-09-18 high8.6 CVE-2026-61551 Icinga 2 is an open source monitoring system. Icinga 2 is an open source monitoring system. 2026-09-18 high8.3 CVE-2026-67436 Linuxfabrik monitoring-plugins provides Python monitoring plugins for Icinga, Nagios, and related monitoring systems. 2026-07-29 high7.6 CVE-2025-27406 Icinga Reporting is the central component for reporting related functionality in the monitoring web frontend and framework Icinga Web 2. versions 2025-03-26 high7.6 CVE-2025-27405 Icinga Web 2 is an open source monitoring web interface, framework and command-line interface. icinga · icinga_web_2 2025-03-26 high7.6 CVE-2025-27404 Icinga Web 2 is an open source monitoring web interface, framework and command-line interface. icinga · icinga_web_2 2025-03-26 high8.3 CVE-2024-24820 Icinga Director is a tool designed to make Icinga 2 configuration handling easy. icinga · icinga 2024-02-09 high7.5 CVE-2022-24716 Icinga Web 2 is an open source monitoring web interface, framework and command-line interface. icinga · icinga_web_2 2022-03-08 high8.5 CVE-2022-24715 Icinga Web 2 is an open source monitoring web interface, framework and command-line interface. icinga · icinga_web_2 2022-03-08 high7.5 CVE-2021-37698 Icinga is a monitoring system which checks the availability of network resources, notifies users of outages, and generates performance data for reporting. icinga · icinga, debian · debian_linux 2021-08-19 high8.8 CVE-2021-32743 Icinga is a monitoring system which checks the availability of network resources, notifies users of outages, and generates performance data for reporting. icinga · icinga, debian · debian_linux 2021-07-15 high8.8 CVE-2021-32739 Icinga is a monitoring system which checks the availability of network resources, notifies users of outages, and generates performance data for reporting. icinga · icinga, debian · debian_linux 2021-07-15 high7.5 CVE-2020-24368 Icinga Icinga Web2 2.0.0 through 2.6.4, 2.7.4 and 2.8.2 has a Directory Traversal vulnerability which allows an attacker to access arbitrary files that are rea… icinga · icinga_web_2, debian · debian_linux, suse · package_hub 2020-08-19 high7.8 CVE-2020-14004 An issue was discovered in Icinga2 before v2.12.0-rc1. icinga · icinga, opensuse · backports_sle, opensuse · leap 2020-06-12 high7.5 CVE-2018-18250 Icinga Web 2 before 2.6.2 allows parameters that break navigation dashlets, as demonstrated by a single '$' character as the Name of a Navigation item. icinga · icinga_web_2 2018-12-17 high8.1 CVE-2018-6535 An issue was discovered in Icinga 2.x through 2.8.1. icinga · icinga 2018-02-27 high7.8 CVE-2018-6533 An issue was discovered in Icinga 2.x through 2.8.1. icinga · icinga 2018-02-27 high7.5 CVE-2018-6532 An issue was discovered in Icinga 2.x through 2.8.1. icinga · icinga 2018-02-27 high7.0 CVE-2017-16933 etc/initsystem/prepare-dirs in Icinga 2.x through 2.8.1 has a chown call for a filename in a user-writable directory, which allows local users to gain privileg… icinga · icinga 2017-11-24 high7.8 CVE-2017-16882 Icinga Core through 1.14.0 initially executes bin/icinga as root but supports configuration options in which this file is owned by a non-root account (and simi… icinga · icinga 2017-11-18 high7.5 CVE-2012-6096 Multiple stack-based buffer overflows in the get_history function in history.cgi in Nagios Core before 3.4.4, and Icinga 1.6.x before 1.6.2, 1.7.x before 1.7.4… nagios · nagios, icinga · icinga 2013-01-22 high7.5 CVE-2012-3441 The database creation script (module/idoutils/db/scripts/create_mysqldb.sh) in Icinga 1.7.1 grants access to all databases to the icinga user, which allows ici… icinga · icinga 2012-08-25

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.