NetSight

Security Dashboard

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

Reset
21 matching advisories · page 1 of 1Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.0 CVE-2026-13484 A vulnerability has been found in MLflow up to 4666cffc7912ea606d592fc38d6a75e2935f65e7. lfprojects · mlflow 2026-06-28 medium6.5 CVE-2026-3198 MLflow 3.9.0 with basic-auth (`--app-name basic-auth`) fails to enforce authorization checks for multiple Gateway API 'list' endpoints. pip · mlflow 2026-06-02 medium6.5 CVE-2026-2734 In mlflow/mlflow versions up to 3.9.0, the `SearchModelVersions` REST API endpoint and the `mlflowSearchModelVersions` GraphQL query lack proper per-model auth… pip · mlflow 2026-05-21 medium4.0 CVE-2026-44430 MCP Registry has an unauthenticated SSRF: HTTP namespace verification dials 6to4 / NAT64 / site-local IPv6 addresses, bypassing private-address allowlist go · github.com/modelcontextprotocol/registry 2026-05-08 medium5.4 CVE-2026-44429 MCP Registry vulnerable to stored XSS in catalogue UI via attribute-quote breakout in publisher-controlled `websiteUrl` go · github.com/modelcontextprotocol/registry 2026-05-08 medium4.7 CVE-2026-44428 The MCP Registry provides MCP clients with a list of MCP servers, like an app store for MCP servers. go · github.com/modelcontextprotocol/registry 2026-05-08 medium4.3 CVE-2026-33866 MLflow is vulnerable to an authorization bypass affecting the AJAX endpoint used to download saved model artifacts. pip · mlflow 2026-04-07 medium5.4 CVE-2026-33865 MLflow is vulnerable to Stored Cross-Site Scripting (XSS) caused by unsafe parsing of YAML-based MLmodel artifacts in its web interface. pip · mlflow 2026-04-07 medium6.1 CVE-2026-34237 MCP Java SDK is the official Java SDK for Model Context Protocol servers and clients. maven · io.modelcontextprotocol.sdk:mcp-core 2026-03-30 medium4.9 CVE-2026-29791 Agentgateway is missing parameter sanitization in MCP to OpenAPI conversion go · github.com/agentgateway/agentgateway 2026-03-05 medium6.4 CVE-2026-27735 mcp-server-git : Path traversal in git_add allows staging files outside repository boundaries pip · mcp-server-git 2026-02-26 medium6.5 CVE-2026-21864 Valkey-Bloom is a Rust based Valkey module which brings a Bloom Filter (Module) data type into the Valkey distributed key-value database. lfprojects · valkey-bloom 2026-02-24 medium4.5 CVE-2025-65105 Apptainer ineffectively applies selinux and apparmor --security options go · github.com/apptainer/apptainer 2025-12-02 medium5.5 CVE-2025-1474 MLflow has Weak Password Requirements pip · mlflow 2025-03-20 medium5.3 CVE-2024-6838 MLflow Uncontrolled Resource Consumption vulnerability pip · mlflow 2025-03-20 medium5.4 CVE-2024-3099 Undefined Behavior in mlflow pip · mlflow 2024-06-06 medium5.4 CVE-2024-4263 MLflow allows low privilege users to delete any artifact pip · mlflow 2024-05-16 medium4.6 CVE-2024-27093 Minder trusts client-provided mapping from repo name to upstream ID go · github.com/stacklok/minder 2024-02-26 medium6.5 CVE-2023-6568 Cross-site Scripting (XSS) in MLflow pip · mlflow 2023-12-07 medium6.1 CVE-2023-38496 Ineffective privileges drop when requesting container network go · github.com/apptainer/apptainer 2023-07-25 medium3.3 CVE-2023-1176 Remote file existence check vulnerability in `mlflow server` and `mlflow ui` CLIs pip · mlflow 2023-03-24

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.