NetSight

Security Dashboard

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

Reset
159 matching advisories · page 5 of 6Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.1 CVE-2026-25960 vLLM is an inference and serving engine for large language models (LLMs). pip · vllm 2026-03-09 critical9.8 CVE-2026-22778 vLLM is an inference and serving engine for large language models (LLMs). pip · vllm 2026-02-02 high7.1 CVE-2026-24779 vLLM vulnerable to Server-Side Request Forgery (SSRF) through MediaConnector pip · vllm 2026-01-27 high8.8 CVE-2026-22807 vLLM affected by RCE via auto_map dynamic module loading during model initialization pip · vllm 2026-01-21 medium6.5 CVE-2026-22773 vLLM is vulnerable to DoS in Idefics3 vision models via image payload with ambiguous dimensions pip · vllm 2026-01-10 high8.7 CVE-2026-56340 vLLM versions >= 0.10.2 and < 0.13.0 are missing sparse tensor validation in multimodal embeddings processing. pip · vllm 2026-01-08 high7.1 CVE-2025-66448 vLLM vulnerable to remote code execution via transformers_utils/get_config pip · vllm 2025-12-01 medium6.5 CVE-2025-62426 vLLM vulnerable to DoS via large Chat Completion or Tokenization requests with specially crafted `chat_template_kwargs` pip · vllm 2025-11-20 high6.5 CVE-2025-62372 vLLM vulnerable to DoS with incorrect shape of multimodal embedding inputs pip · vllm 2025-11-20 high8.8 CVE-2025-62164 vLLM is an inference and serving engine for large language models (LLMs). pip · vllm 2025-11-20 medium6.5 CVE-2025-61620 vLLM: Resource-Exhaustion (DoS) through Malicious Jinja Template in OpenAI-Compatible Server pip · vllm 2025-10-07 high7.1 CVE-2025-6242 A Server-Side Request Forgery (SSRF) vulnerability exists in the MediaConnector class within the vLLM project's multimodal feature set. pip · vllm 2025-10-07 high7.5 CVE-2025-59425 vLLM is an inference and serving engine for large language models (LLMs). pip · vllm 2025-10-07 high8.8 CVE-2025-9141 vLLM has remote code execution vulnerability in the tool call parser for Qwen3-Coder pip · vllm 2025-08-21 high7.5 CVE-2025-48956 vLLM is an inference and serving engine for large language models (LLMs). pip · vllm 2025-08-21 medium6.5 CVE-2025-48944 vLLM is an inference and serving engine for large language models (LLMs). pip · vllm 2025-05-28 medium6.5 CVE-2025-48943 vLLM is an inference and serving engine for large language models (LLMs). pip · vllm 2025-05-28 medium6.5 CVE-2025-48942 vLLM is an inference and serving engine for large language models (LLMs). pip · vllm 2025-05-28 medium4.2 CVE-2025-46722 vLLM is an inference and serving engine for large language models (LLMs). pip · vllm 2025-05-28 low2.6 CVE-2025-46570 Potential Timing Side-Channel Vulnerability in vLLM’s Chunk-Based Prefix Caching pip · vllm 2025-05-28 medium4.3 GHSA-j828-28rj-hfhp vLLM vulnerable to Regular Expression Denial of Service pip · vllm 2025-05-28 medium6.5 CVE-2025-48887 vLLM, an inference and serving engine for large language models (LLMs), has a Regular Expression Denial of Service (ReDoS) vulnerability in the file `vllm/entr… pip · vllm 2025-05-28 critical9.8 CVE-2025-47277 vLLM, an inference and serving engine for large language models (LLMs), has an issue in versions 0.6.5 through 0.8.4 that ONLY impacts environments using the `… pip · vllm 2025-05-20 high8.0 CVE-2025-30165 Remote Code Execution Vulnerability in vLLM Multi-Node Cluster Configuration pip · vllm 2025-05-06 medium6.5 CVE-2025-46560 vLLM is a high-throughput and memory-efficient inference and serving engine for LLMs. pip · vllm 2025-04-29 critical10.0 CVE-2025-32444 vLLM is a high-throughput and memory-efficient inference and serving engine for LLMs. pip · vllm 2025-04-29 high7.5 CVE-2025-30202 vLLM is a high-throughput and memory-efficient inference and serving engine for LLMs. pip · vllm 2025-04-29 critical9.8 GHSA-ggpf-24jw-3fcw CVE-2025-24357 Malicious model remote code execution fix bypass with PyTorch < 2.6.0 pip · vllm 2025-04-23 medium6.5 GHSA-hf3c-wxg2-49q9 vLLM vulnerable to Denial of Service by abusing xgrammar cache pip · vllm 2025-04-15 critical9.8 CVE-2024-9053 vllm-project vllm version 0.6.0 contains a vulnerability in the AsyncEngineRPCServer() RPC server entrypoints. pip · vllm 2025-03-20

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.