NetSight

Security Dashboard

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

Reset
264 matching advisories · page 2 of 9Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.8 CVE-2026-50260 A use-after-free flaw was found in the X.Org X server and Xwayland in FreeCounter(). x.org · x_server, x.org · xwayland, redhat · enterprise_linux 2026-06-05 high7.8 CVE-2026-50259 A stack-based buffer overflow flaw was found in the X.Org X server and Xwayland. x.org · x_server, x.org · xwayland, redhat · enterprise_linux 2026-06-05 high7.8 CVE-2026-50258 A stack-based buffer overflow flaw was found in the X.Org X server and Xwayland. x.org · x_server, x.org · xwayland, redhat · enterprise_linux 2026-06-05 high7.8 CVE-2026-50257 A use-after-free flaw was found in the X.Org X server and Xwayland in miSyncDestroyFence(). x.org · x_server, x.org · xwayland, redhat · enterprise_linux 2026-06-05 high7.8 CVE-2026-50256 A stack-based buffer overflow flaw was found in the X.Org X server and Xwayland. x.org · x_server, x.org · xwayland, redhat · enterprise_linux 2026-06-05 medium6.1 CVE-2026-34002 A flaw was found in the X.Org X server. x.org · x_server, redhat · enterprise_linux, Red Hat · Red Hat Enterprise Linux 10.0 Extended Update Support +19 2026-05-05 medium6.1 CVE-2026-34000 A flaw was found in the X.Org X server. x.org · x_server, redhat · enterprise_linux, Red Hat · Red Hat Enterprise Linux 10.0 Extended Update Support +21 2026-05-05 high7.8 CVE-2026-34003 A flaw was found in the X.Org X server's XKB key types request validation. 2026-04-23 high7.8 CVE-2026-34001 A flaw was found in the X.Org X server. 2026-04-23 high7.8 CVE-2026-33999 A flaw was found in the X.Org X server. 2026-04-23 high8.7 CVE-2025-14727 A vulnerability exists in NGINX Ingress Controller's nginx.org/rewrite-target annotation validation. f5 · nginx_ingress_controller, F5 · NGINX Ingress Controller 2025-12-17 high7.3 CVE-2025-62230 A flaw was discovered in the X.Org X server’s X Keyboard (Xkb) extension when handling client resource cleanup. x.org · x_server, x.org · xwayland, ibm · vios +8 2025-10-30 high7.3 CVE-2025-62229 A flaw was found in the X.Org X server and Xwayland when processing X11 Present extension notifications. 2025-10-30 high7.3 CVE-2025-62231 A flaw was identified in the X.Org X server’s X Keyboard (Xkb) extension where improper bounds checking in the XkbSetCompatMap() function can cause an unsigned… x.org · x_server, x.org · xwayland, ibm · vios +8 2025-10-30 high7.7 CVE-2022-49737 In X.Org X server 20.11 through 21.1.16, when a client application uses easystroke for mouse gestures, the main thread modifies various data structures used by… X.Org X server 2025-03-16 high7.8 CVE-2025-26601 A use-after-free flaw was found in X.Org and Xwayland. tigervnc · tigervnc, x.org · x_server, x.org · xwayland +1 2025-02-25 high7.8 CVE-2025-26600 A use-after-free flaw was found in X.Org and Xwayland. tigervnc · tigervnc, x.org · x_server, x.org · xwayland +1 2025-02-25 high7.8 CVE-2025-26599 An access to an uninitialized pointer flaw was found in X.Org and Xwayland. tigervnc · tigervnc, x.org · x_server, x.org · xwayland +1 2025-02-25 high7.8 CVE-2025-26598 An out-of-bounds write flaw was found in X.Org and Xwayland. tigervnc · tigervnc, x.org · x_server, x.org · xwayland +1 2025-02-25 high7.8 CVE-2025-26597 A buffer overflow flaw was found in X.Org and Xwayland. tigervnc · tigervnc, x.org · x_server, x.org · xwayland +1 2025-02-25 high7.8 CVE-2025-26596 A heap overflow flaw was found in X.Org and Xwayland. tigervnc · tigervnc, x.org · x_server, x.org · xwayland +1 2025-02-25 high7.8 CVE-2025-26595 A buffer overflow flaw was found in X.Org and Xwayland. tigervnc · tigervnc, x.org · x_server, x.org · xwayland +1 2025-02-25 high7.8 CVE-2025-26594 A use-after-free flaw was found in X.Org and Xwayland. tigervnc · tigervnc, x.org · x_server, x.org · xwayland +1 2025-02-25 high7.8 CVE-2024-9632 A flaw was found in the X.org server. 2024-10-30 high7.3 CVE-2024-31082 A heap-based buffer over-read vulnerability was found in the X.org server's ProcAppleDRICreatePixmap() function. 2024-04-04 high7.3 CVE-2024-31081 A heap-based buffer over-read vulnerability was found in the X.org server's ProcXIPassiveGrabDevice() function. 2024-04-04 high7.3 CVE-2024-31080 A heap-based buffer over-read vulnerability was found in the X.org server's ProcXIGetSelectedEvents() function. 2024-04-04 high7.8 CVE-2024-21886 A heap buffer overflow flaw was found in the DisableDevice function in the X.Org server. 2024-02-28 high7.8 CVE-2024-21885 A flaw was found in X.Org server. 2024-02-28 high7.8 CVE-2024-0229 An out-of-bounds memory access flaw was found in the X.Org server. x.org · x_server, x.org · xwayland, fedoraproject · fedora +5 2024-02-09

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.