NetSight

Security Dashboard

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

Reset
437 matching advisories · page 2 of 15Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2026-16140 OpenBMC's IPMI implementation, phosphor-net-ipmid, is vulnerable to a logic flaw where the authorization context of an existing session can be replaced with a … 2026-09-15 high7.3 CVE-2025-15679 Under certain circumstances such as reset to factory default operation, the BMC root account is made active without a password on BullSequana XH3406 and XH3515. 2026-09-11 low3.1 CVE-2026-87521 Information leak in WebMCP in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to obtain cross-origin da… google · chrome 2026-09-09 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 high7.5 CVE-2026-85505 ipmi-oem in FreeIPMI before 1.6.19 has a stack-based buffer over-read in ipmi_oem_fujitsu_get_sel_entry_long_text in ipmi-oem/ipmi-oem-fujitsu.c when a BMC pro… FreeIPMI 2026-09-04 medium6.8 CVE-2026-18849 IBM OpenBMC FW1060.00 through FW1060.80 is affected by a vulnerability in the BMC firmware update process. ibm · openbmc, ibm · power_system_e1050_\(9043-mrx\)_firmware, ibm · power_system_l1022_\(9786-22h\)_firmware +6 2026-08-19 high8.2 CVE-2026-17494 IBM Power Systems Firmware FW1120.00, and FW1110.00 through FW1110.30 is affected by a vulnerability in the interface between the BMC and the host system. ibm · power_system_s1122_\(9824-22a\)_firmware, ibm · power_system_s1124_\(9824-42a\)_firmware, ibm · power_system_s1122s_\(9824-22b\)_firmware +7 2026-08-19 medium6.5 CVE-2026-17854 Insufficient policy enforcement in WebMCP in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to bypass same origin policy via a crafted HTML pag… google · chrome 2026-07-30 medium4.5 CVE-2026-8058 IBM OPENBMC FW1110.00 through FW1110.20, and FW1060.00 through FW1060.71 allows a user to supply a password with a resource dump request stores that password i… ibm · power_system_s1122_\(9824-22a\)_firmware, ibm · power_system_s1124_\(9824-42a\)_firmware, ibm · power_system_s1122s_\(9824-22b\)_firmware +9 2026-07-28 medium6.5 CVE-2026-7868 IBM OPENBMC FW1110.00 through FW1110.20, and FW1060.00 through FW1060.71 allows ReadOnly users to escalate privileges and give themselves administrator privile… ibm · power_system_s1122_\(9824-22a\)_firmware, ibm · power_system_s1124_\(9824-42a\)_firmware, ibm · power_system_s1122s_\(9824-22b\)_firmware +9 2026-07-28 medium5.5 CVE-2026-64504 In the Linux kernel, the following vulnerability has been resolved: iio: accel: bmc150: clamp the device-reported FIFO frame count __bmc150_accel_fifo_flush() … linux · linux_kernel 2026-07-25 high8.8 CVE-2026-16806 Use after free in WebMCP in Google Chrome prior to 150.0.7871.186 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. google · chrome 2026-07-23 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-5vpm-fwr5-hjmv Malicious code in libmcencodeed (PyPI)Malware pip · libmcencodeed 2026-07-21

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.