NetSight

Security Dashboard

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

Reset
18 matching advisories · page 1 of 1Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.8 GHSA-hhww-mrg2-969h LiteLLM vulnerable to reflected XSS in /sso/debug/callback pip · litellm 25 days ago medium6.3 CVE-2026-108575 A vulnerability has been found in BerriAI LiteLLM up to 1.94.0. BerriAI LiteLLM 41 days ago medium4.3 CVE-2026-108574 A flaw has been found in BerriAI LiteLLM up to 1.95.0. BerriAI LiteLLM 41 days ago medium5.3 CVE-2026-59823 LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. pip · litellm 2026-09-16 medium6.5 CVE-2026-84377 LiteLLM: Authenticated SSRF and provider-credential exfiltration via unvalidated request-body routing parameters pip · litellm 2026-09-02 medium6.5 CVE-2026-59820 LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. pip · litellm 2026-07-08 medium4.9 CVE-2026-59819 LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. pip · litellm 2026-07-08 medium4.3 CVE-2026-12799 BerriAI litellm: UI User Enumeration leads to System-Wide Information Disclosure pip · litellm 2026-06-21 medium6.3 CVE-2026-12798 BerriAI litellm has SSRF via Unvalidated spec_path URL in MCP OpenAPI Spec Loader pip · litellm 2026-06-21 medium6.3 CVE-2026-12797 BerriAI litellm has Security Feature Bypass in BannedKeywords and AzureContentSafety Guardrails via call_type Mismatch on Async Endpoints pip · litellm 2026-06-21 medium6.3 CVE-2026-12796 BerriAI litellm: SSO Login Does Not Invalidate Previous UI Session Tokens pip · litellm 2026-06-21 medium6.3 CVE-2026-12774 A security vulnerability has been detected in BerriAI litellm up to 1.82.2. litellm · litellm 2026-06-21 medium6.3 CVE-2026-12772 LiteLLM: PROXY_ADMIN database API Key Generator Has Insufficient Session Expiration pip · litellm 2026-06-21 medium5.0 CVE-2026-12771 A vulnerability was identified in BerriAI litellm up to 1.82.2. pip · litellm 2026-06-21 medium5.4 CVE-2026-12770 A vulnerability was determined in BerriAI litellm up to 1.63.1. pip · litellm 2026-06-21 medium5.4 CVE-2025-45809 SQL Injection vulnerability in BerriAI LiteLLM before 1.81.0 allows attackers to execute arbitrary commands via the key parameter to the "/key/block" and "/key… litellm · litellm 2025-07-03 medium5.3 CVE-2024-5710 litellm vulnerable to improper access control in team management pip · litellm 2024-06-27 medium4.9 CVE-2024-4890 SQL injection in litellm pip · litellm 2024-06-06

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.