NetSight

Security Dashboard

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

Reset
14 matching advisories · page 1 of 1Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.9 CVE-2026-16791 A temporary file creation vulnerability in the Linux version of Lenovo XClarity Essentials OneCLI 5.5.0 and below could allow a local low-privileged attacker t… 2026-08-04 low2.8 CVE-2026-0520 A potential vulnerability was reported in the Lenovo FileZ Android application that, under certain conditions, could allow a local authenticated user to retrie… lenovo · filez 2026-03-11 low3.2 CVE-2025-14058 A potential missing authentication vulnerability was reported in some Lenovo Tablets that could allow an unauthorized user with physical access to modify Contr… 2026-01-14 low3.1 CVE-2025-6026 An improper certificate validation vulnerability was reported in the Lenovo Universal Device Client (UDC) that could allow a user capable of intercepting netwo… 2025-10-15 low2.8 CVE-2024-4786 An improper validation vulnerability was reported in the Lenovo Tab K10 that could allow a specially crafted application to keep the device on. 2024-07-26 low2.0 CVE-2024-23591 ThinkSystem SR670V2 servers manufactured from approximately June 2021 to July 2023 were left in Manufacturing Mode which could allow an attacker with privilege… lenovo · thinksystem_sr670_v2_firmware 2024-02-16 low3.3 CVE-2023-5081 An information disclosure vulnerability was reported in the Lenovo Tab M8 HD that could allow a local application to gather a non-resettable device identifier. lenovo · tab_m8_hd_tb8505f_firmware, lenovo · tab_m8_hd_tb8505fs_firmware, lenovo · tab_m8_hd_tb8505x_firmware +1 2024-01-19 low2.7 CVE-2022-34888 The Remote Mount feature can potentially be abused by valid, authenticated users to make connections to internal services that may not normally be accessible t… lenovo · thinkagile_vx3331_firmware, lenovo · thinkagile_hx_enclosure_certified_node_firmware, lenovo · thinkagile_hx1021_firmware +9 2023-01-30 low2.4 CVE-2020-8352 In some Lenovo Desktop models, the Configuration Change Detection BIOS setting failed to detect SATA configuration changes. lenovo · thinkcentre_e73_firmware, lenovo · thinkcentre_m73_firmware, lenovo · qitian_4500_firmware +9 2020-11-11 low2.4 CVE-2020-8341 In Lenovo systems, SMM BIOS Write Protection is used to prevent writes to SPI Flash. lenovo · thinkpad_t490_\(20nx\)_firmware, lenovo · thinkpad_t490_\(20qx\)_firmware, lenovo · thinkpad_t490_\(20rx\)_firmware +7 2020-09-01 low3.3 CVE-2019-6156 In Lenovo systems, SMM BIOS Write Protection is used to prevent writes to SPI Flash. lenovo · 510-15ikl_firmware, lenovo · 510s-08ikl_firmware, lenovo · ideacentre_300-20ish_firmware +9 2019-04-10 low3.3 CVE-2017-3741 In the Lenovo Power Management driver before 1.67.12.24, a local user may alter the trackpoint's firmware and stop the trackpoint from functioning correctly. lenovo · power_management 2017-06-04 low2.1 CVE-2015-3320 Lenovo USB Enhanced Performance Keyboard software before 2.0.2.2 includes active debugging code in SKHOOKS.DLL, which allows local users to obtain keypress inf… lenovo · usb_enhanced_performance_keyboard 2015-04-16 low2.1 CVE-2008-3894 IBM Lenovo firmware 7CETB5WW 2.05 stores pre-boot authentication passwords in the BIOS Keyboard buffer and does not clear this buffer after use, which allows l… ibm · lenovo_7cetb5ww 2008-09-03

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.