NetSight

Security Dashboard

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

Reset
64 matching advisories · page 2 of 3Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2025-0453 MLflow Uncontrolled Resource Consumption vulnerability pip · mlflow 2025-03-20 high7.5 CVE-2024-8859 MLflow has a Local File Read/Path Traversal in dbfs pip · mlflow 2025-03-20 high7.0 CVE-2024-27134 MLflow's excessive directory permissions allow local privilege escalation pip · mlflow 2024-11-25 high7.5 CVE-2024-2928 Local File Inclusion in mlflow pip · mlflow 2024-06-06 high8.8 CVE-2024-37061 MLFlow improper input validation pip · mlflow 2024-06-04 high8.8 CVE-2024-37060 MLFlow unsafe deserialization pip · mlflow 2024-06-04 high8.8 CVE-2024-37059 MLFlow unsafe deserialization pip · mlflow 2024-06-04 high8.8 CVE-2024-37058 MLFlow unsafe deserialization pip · mlflow 2024-06-04 high8.8 CVE-2024-37057 MLFlow unsafe deserialization pip · mlflow 2024-06-04 high8.8 CVE-2024-37056 MLFlow unsafe deserialization pip · mlflow 2024-06-04 high8.8 CVE-2024-37055 MLFlow unsafe deserialization pip · mlflow 2024-06-04 high8.8 CVE-2024-37054 MLFlow unsafe deserialization pip · mlflow 2024-06-04 high8.8 CVE-2024-37053 MLFlow unsafe deserialization pip · mlflow 2024-06-04 high8.8 CVE-2024-37052 MLFlow unsafe deserialization pip · mlflow 2024-06-04 high7.5 CVE-2024-3848 MLflow has a Local File Read/Path Traversal bypass pip · mlflow 2024-05-16 high7.5 CVE-2024-1594 mlflow vulnerable to Path Traversal pip · mlflow 2024-04-16 high7.5 CVE-2024-1593 mlflow vulnerable to Path Traversal pip · mlflow 2024-04-16 high8.1 CVE-2024-1560 mlflow vulnerable to Path Traversal pip · mlflow 2024-04-16 high7.5 CVE-2024-1558 mlflow vulnerable to Path Traversal pip · mlflow 2024-04-16 high7.5 CVE-2024-1483 mlflow Path Traversal vulnerability pip · mlflow 2024-04-16 high7.1 CVE-2024-27916 `GetRepositoryByName`, `DeleteRepositoryByName` and `GetArtifactByName` allow access of arbitrary repositories in Minder by any authenticated user go · github.com/stacklok/minder 2024-03-05 high7.5 CVE-2023-6977 MLflow Local File Disclosure Vulnerability pip · mlflow 2023-12-20 high8.8 CVE-2023-6976 MLflow Path Traversal Vulnerability pip · mlflow 2023-12-20 high8.8 CVE-2023-6940 mlflow Command Injection vulnerability pip · mlflow 2023-12-19 high7.5 CVE-2023-6909 MLflow Path Traversal Vulnerability pip · mlflow 2023-12-18 high8.8 CVE-2023-6753 Path traversal in MLflow pip · mlflow 2023-12-13 high8.8 CVE-2023-6709 Jinja2 template injection in mlflow pip · mlflow 2023-12-12 high7.5 CVE-2023-43472 Information exposure in MLflow pip · mlflow 2023-12-05 high8.8 CVE-2023-4033 mlflow vulnerable to OS Command Injection pip · mlflow 2023-08-01 high7.5 CVE-2023-30172 mflow vulnerable to directory traversal pip · mlflow 2023-05-11

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.