NetSight

Security Dashboard

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

Reset
27 matching advisories · page 1 of 1Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
unscored CVE-2026-99417 In the Linux kernel, the following vulnerability has been resolved: ovl: fix a torn path in ovl_get_redirect() A hard link of a metacopy file that races with a… Linux · Linux 2 days ago unscored CVE-2026-99412 In the Linux kernel, the following vulnerability has been resolved: xfs: avoid cross-rtgroup reaping after a repair LOLLM notices that the extents stored in a … Linux · Linux 2 days ago unscored CVE-2026-16487 Rejected reason: Red Hat Product Security has determined that this is not a vulnerability in bootc or containers-common. 33 days ago unscored CVE-2026-88836 Rejected reason: Red Hat Product Security determined this is not a security vulnerability. 39 days ago unscored CVE-2026-104710 Rejected reason: Duplicate of CVE-2026-71364, which was publicly disclosed and fixed in Red Hat Ansible Automation Platform on 2026-08-24. 40 days ago unscored CVE-2026-90264 In the Linux kernel, the following vulnerability has been resolved: btrfs: always wait for ordered extents to avoid OE races [BUG] Syzbot reported a bug that t… 2026-09-17 unscored CVE-2026-53681 Rejected reason: Red Hat Product Security has come to the conclusion that this CVE is not needed. 2026-09-17 unscored CVE-2026-53679 Rejected reason: Red Hat Product Security has come to the conclusion that this CVE is not needed. 2026-09-17 unscored CVE-2026-11874 Rejected reason: Red Hat Product Security has come to the conclusion that this CVE is not needed. 2026-09-17 unscored CVE-2026-80219 Rejected reason: Red Hat Product Security has come to the conclusion that this CVE is not needed. 2026-09-08 unscored CVE-2026-15926 Rejected reason: Red Hat Product Security has determined that this CVE ID is not needed 2026-09-03 unscored CVE-2026-13081 Rejected reason: Red Hat is not the CNA for PHP. 2026-08-24 unscored CVE-2026-13047 Rejected reason: Red Hat is not the CNA for PHP. 2026-08-24 unscored CVE-2026-19582 Rejected reason: Red Hat Product Security has come to the conclusion that this CVE is false due to upstream security policy. 2026-08-20 unscored CVE-2026-72540 Rejected reason: Red Hat CNA-LR concluded that this CVE is not valid. 2026-08-11 unscored CVE-2026-72585 Rejected reason: Red Hat CNA-LR concluded that this CVE is not valid. 2026-08-10 unscored CVE-2026-72568 Rejected reason: Red Hat CNA-LR concluded that this CVE is not valid. 2026-08-10 unscored CVE-2026-71245 Rejected reason: Red Hat CNA-LR concluded that this CVE is not valid. 2026-08-05 unscored CVE-2026-50238 Rejected reason: Red Hat Product Security has concluded that this CVE is not required. 2026-07-03 unscored CVE-2026-13325 Rejected reason: Red Hat Product Security has come to the conclusion that this CVE is not needed. 2026-06-26 unscored CVE-2023-4533 Rejected reason: Red Hat Product Security has come to the conclusion that this CVE is not needed. 2025-04-30 unscored CVE-2025-3269 Rejected reason: Red Hat Product Security has come to the conclusion that this CVE is not needed. 2025-04-30 unscored CVE-2025-2156 Rejected reason: Red Hat Product Security has come to the conclusion that this CVE is not needed. 2025-04-30 unscored CVE-2024-12840 Rejected reason: Red Hat Product Security has come to the conclusion that this CVE is not needed. 2024-12-20 unscored CVE-2024-1271 Rejected reason: This CVE was previously published at https://bugzilla.redhat.com/show_bug.cgi?id=2262978 but later rejected for the following reason: The flaw… 2024-11-19 unscored CVE-2024-8421 Rejected reason: Red Hat Product Security has come to the conclusion that this CVE is not needed. 2024-10-01 unscored CVE-2022-0931 Rejected reason: Red Hat Product Security does not consider this to be a vulnerability. 2024-02-08

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.