NetSight

Security Dashboard

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

Reset
437 matching advisories · page 4 of 15Index updated 6 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.2 CVE-2025-8076 There is a vulnerability in the Supermicro BMC web function at Supermicro MBD-X13SEDW-F. 2025-11-18 medium5.4 CVE-2025-7704 Supermicro BMC Insyde SMASH shell program has a stacked-based overflow vulnerability 2025-11-13 high7.2 CVE-2025-7937 There is a vulnerability in the Supermicro BMC firmware validation logic at Supermicro MBD-X12STW . 2025-09-19 high7.2 CVE-2025-6198 There is a vulnerability in the Supermicro BMC firmware validation logic at Supermicro MBD-X13SEM-F . 2025-09-19 medium5.3 CVE-2025-55117 A stack-based buffer overflow can be remotely triggered when formatting an error message in the Control-M/Agent when SSL/TLS communication is configured. bmc · control-m\/agent 2025-09-16 high8.8 CVE-2025-55116 A buffer overflow in the Control-M/Agent can lead to a local privilege escalation when an attacker has access to the system running the Agent. bmc · control-m\/agent 2025-09-16 high8.8 CVE-2025-55115 A path traversal in the Control-M/Agent can lead to a local privilege escalation when an attacker has access to the system running the Agent. bmc · control-m\/agent 2025-09-16 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 high7.4 CVE-2025-55112 Out-of-support Control-M/Agent versions 9.0.18 to 9.0.20 (and potentially earlier unsupported versions) that are configured to use the non-default Blowfish cry… bmc · control-m\/agent 2025-09-16 medium5.5 CVE-2025-55111 Certain files with overly permissive permissions were identified in the out-of-support Control-M/Agent versions 9.0.18 to 9.0.20 and potentially earlier unsupp… bmc · control-m\/agent 2025-09-16 critical9.0 CVE-2025-55109 An authentication bypass vulnerability exists in the out-of-support Control-M/Agent versions 9.0.18 to 9.0.20 and potentially earlier unsupported versions when… bmc · control-m\/agent 2025-09-16 high7.8 CVE-2025-39785 In the Linux kernel, the following vulnerability has been resolved: drm/hisilicon/hibmc: fix irq_request()'s irq name variable is local The local variable is p… linux · linux_kernel 2025-09-11 medium5.5 CVE-2025-39772 In the Linux kernel, the following vulnerability has been resolved: drm/hisilicon/hibmc: fix the hibmc loaded failed bug When hibmc loaded failed, the driver u… linux · linux_kernel, debian · debian_linux 2025-09-11 medium5.5 CVE-2025-38720 In the Linux kernel, the following vulnerability has been resolved: net: hibmcge: fix rtnl deadlock issue Currently, the hibmcge netdev acquires the rtnl_lock … linux · linux_kernel 2025-09-04 medium5.5 CVE-2025-38719 In the Linux kernel, the following vulnerability has been resolved: net: hibmcge: fix the division by zero issue When the network port is down, the queue is re… linux · linux_kernel 2025-09-04 low3.8 CVE-2025-48709 BMC Control-M/Server 9.0.21.300 displays cleartext database credentials in process lists and logs. bmc · control-m\/server 2025-08-07 high7.1 CVE-2012-10024 XBMC version 11.0 contains a path traversal vulnerability in its embedded HTTP server. 2025-08-05 medium5.5 CVE-2022-49745 In the Linux kernel, the following vulnerability has been resolved: fpga: m10bmc-sec: Fix probe rollback Handle probe error rollbacks properly to avoid leaks. linux · linux_kernel 2025-03-27 medium6.5 CVE-2025-29781 Bare Metal Operator (BMO) can expose any secret from other namespaces via BMCEventSubscription CRD go · github.com/metal3-io/baremetal-operator/apis 2025-03-17 medium4.2 CVE-2024-34398 An issue was discovered in BMC Remedy Mid Tier 7.6.04. bmc · remedy_mid-tier 2025-03-12 high7.7 CVE-2024-46933 An issue was discovered in Atos Eviden BullSequana XH2140 BMC before C4EM-125: OMF_C4E 101.05.0014. 2025-02-20 medium4.3 CVE-2025-20097 Uncaught exception in OpenBMC Firmware for the Intel(R) Server M50FCP Family and Intel(R) Server D50DNP Family before version R01.02.0002 may allow an authenti… 2025-02-12 high8.2 CVE-2023-31276 Heap-based buffer overflow in BMC Firmware for the Intel(R) Server Board S2600WF, Intel(R) Server Board S2600ST, Intel(R) Server Board S2600BP, before version … 2025-02-12 high7.3 CVE-2023-29164 Improper access control in BMC Firmware for the Intel(R) Server Board S2600WF, Intel(R) Server Board S2600ST, Intel(R) Server Board S2600BP, before version 02.… 2025-02-12 high7.2 CVE-2024-10237 There is a vulnerability in the BMC firmware image authentication design at Supermicro MBD-X12DPG-OA6 . 2025-02-04 high7.8 CVE-2022-49029 In the Linux kernel, the following vulnerability has been resolved: hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails Smatch report warning as … linux · linux_kernel 2024-10-21 critical9.8 CVE-2024-34399 **UNSUPPORTED WHEN ASSIGNED** An issue was discovered in BMC Remedy Mid Tier 7.6.04. bmc · remedy_mid-tier 2024-09-18 medium6.7 CVE-2023-49144 Out of bounds read in OpenBMC Firmware for some Intel(R) Server Platforms before versions egs-1.15-0, bhs-0.27 may allow a privileged user to potentially enabl… 2024-08-14 medium4.3 CVE-2023-35123 Uncaught exception in OpenBMC Firmware for some Intel(R) Server Platforms before versions egs-1.14-0, bhs-0.27 may allow an authenticated user to potentially e… 2024-08-14 high7.5 CVE-2024-35124 A vulnerability in the combination of the OpenBMC's FW1050.00 through FW1050.10, FW1030.00 through FW1030.50, and FW1020.00 through FW1020.60 default password … ibm · openbmc 2024-08-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.