NetSight

Security Dashboard

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

Reset
69 matching advisories · page 1 of 3Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2026-18450 The BMC does not correctly enforce integrity and encryption requirements for IPMI commands. 25 days ago critical9.0 CVE-2026-111283 BMC Helix Network Management on-prem 26.3.00 before 26.3.01 contains an authentication bypass vulnerability that allows unauthenticated attackers to log in as … BMC Helix Network Management on-prem 37 days ago critical GHSA-327g-rcr8-hp3p Malware in bmc-i18n-extract-cliMalware npm · bmc-i18n-extract-cli 2026-09-07 critical GHSA-997w-vpm2-ww7x Malware in bmc-translate-utilsMalware npm · bmc-translate-utils 2026-09-07 critical9.8 CVE-2026-85509 FreeIPMI before 1.6.19 has a stack-based buffer overflow in _read_fru_data in libfreeipmi/fru/ipmi-fru.c when a BMC returns more bytes than requested. FreeIPMI 2026-09-04 critical GHSA-rwqv-55m9-qgqc Malicious code in tplgtbmcultra (PyPI)Malware pip · tplgtbmcultra 2026-07-21 critical GHSA-4w35-h2g7-vv3r Malicious code in py-prooflibmc (PyPI)Malware pip · py-prooflibmc 2026-07-21 critical GHSA-wjc5-jmwp-p522 Malicious code in py-libmcstring (PyPI)Malware pip · py-libmcstring 2026-07-21 critical GHSA-h96w-2r2w-p78r Malicious code in libmcint (PyPI)Malware pip · libmcint 2026-07-21 critical GHSA-37jw-rvpj-3jp5 Malicious code in libmcmine (PyPI)Malware pip · libmcmine 2026-07-21 critical GHSA-hr7x-4646-hr32 Malicious code in libmcpingstudy (PyPI)Malware pip · libmcpingstudy 2026-07-21 critical GHSA-56gv-w36g-p92g Malicious code in libmcpipver (PyPI)Malware pip · libmcpipver 2026-07-21 critical GHSA-9qq6-jgq6-jvw6 Malicious code in libmclibed (PyPI)Malware pip · libmclibed 2026-07-21 critical GHSA-mj2g-7vxx-x9p9 Malicious code in libmcpongvm (PyPI)Malware pip · libmcpongvm 2026-07-21 critical GHSA-5377-jrx7-35q6 Malicious code in libmcrever (PyPI)Malware pip · libmcrever 2026-07-21 critical GHSA-fgvj-v978-vpxw Malicious code in libmcrandomre (PyPI)Malware pip · libmcrandomre 2026-07-21 critical GHSA-m46c-qp7j-x3x2 Malicious code in libmcpywcontrol (PyPI)Malware pip · libmcpywcontrol 2026-07-21 critical GHSA-475f-fhrv-6m7w Malicious code in libmcpep (PyPI)Malware pip · libmcpep 2026-07-21 critical GHSA-x55w-3jq9-wmg5 Malicious code in libmcrandompep (PyPI)Malware pip · libmcrandompep 2026-07-21 critical GHSA-pm4r-mmh3-mvvw Malicious code in libmcmaskkill (PyPI)Malware pip · libmcmaskkill 2026-07-21 critical GHSA-w66w-m324-xg34 Malicious code in libmchydraint (PyPI)Malware pip · libmchydraint 2026-07-21 critical GHSA-pprp-pgrx-97hq Malicious code in libmcget (PyPI)Malware pip · libmcget 2026-07-21 critical GHSA-qgp7-hjrq-qcff Malicious code in libmccraftpush (PyPI)Malware pip · libmccraftpush 2026-07-21 critical GHSA-2gg4-r8jp-f54f Malicious code in libmcintel (PyPI)Malware pip · libmcintel 2026-07-21 critical GHSA-jr2f-c4h9-42j6 Malicious code in libmccchacked (PyPI)Malware pip · libmccchacked 2026-07-21 critical GHSA-88v6-r63p-x9fh Malicious code in libmccandyhttp (PyPI)Malware pip · libmccandyhttp 2026-07-21 critical GHSA-5vpm-fwr5-hjmv Malicious code in libmcencodeed (PyPI)Malware pip · libmcencodeed 2026-07-21 critical GHSA-mv24-m6hc-2m79 Malicious code in libintlibmc (PyPI)Malware pip · libintlibmc 2026-07-21 critical9.8 CVE-2026-23781 An issue was discovered in BMC Control-M/MFT 9.0.20 through 9.0.22. bmc · control-m\/managed_file_transfer 2026-04-10 critical9.0 CVE-2025-55113 If the Access Control List is enforced by the Control-M/Agent and the C router is in use (default in Out-of-support Control-M/Agent versions 9.0.18 to 9.0.20 a… bmc · control-m\/agent 2025-09-16

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.