NetSight

Security Dashboard

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

Reset
33 matching advisories · page 1 of 2Index updated 9 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.0 CVE-2026-119978 Flowise through 3.1.4 contains a sandbox escape vulnerability that allows authenticated users to execute OS commands by abusing allowlisted langchain and mammo… FlowiseAI · Flowise 22 days ago critical9.8 CVE-2026-75128 Langchain-Chatchat through 0.3.1.3 exposes a POST /tools/call API endpoint that invokes any registered tool by name without authentication, leaving the always-… Langchain-Chatchat 33 days ago critical9.8 CVE-2026-51884 The /knowledge_base/upload_temp_docs temporary document upload endpoint in Langchain Chatchat 0.3.1 is vulnerable to path traversal. 51 days ago critical9.1 CVE-2026-51883 The knowledge base creation and document upload interfaces in Langchain-Chatchat 0.3.0;0.3.1 is vulnerable to path traversal. 51 days ago critical9.1 CVE-2026-51882 The OpenAI-compatible file upload endpoint `/v1/files` in Langchain-Chatchat 0.3.0 is vulnerable to path traversal. 51 days ago critical GHSA-h82v-pqpv-jr3r Malicious code in azure-langchain-example (PyPI)Malware pip · azure-langchain-example 54 days ago critical GHSA-f6f5-m9qw-v738 Malicious code in langchain-core-mcp (PyPI)Malware pip · langchain-core-mcp, pip · langchain-core-mcp 2026-07-21 critical9.3 CVE-2025-68664 LangChain serialization injection vulnerability enables secret extraction in dumps/loads APIs pip · langchain-core 2025-12-23 critical9.8 CVE-2025-9556 Langchaingo supports the use of jinja2 syntax when parsing prompts, which is in turn parsed using the gonja library v1.5.3. 2025-09-12 critical9.8 CVE-2025-45150 Insecure permissions in LangChain-ChatGLM-Webui commit ef829 allows attackers to arbitrarily view and download sensitive files via supplying a crafted request. x-d_lab · langchain-chatglm-webui 2025-08-01 critical9.8 CVE-2025-46059 langchain-ai v0.3.51 was discovered to contain an indirect prompt injection vulnerability in the GmailToolkit component. 2025-07-29 critical GHSA-f2cq-6rfj-2m8v Malware in paypal-examples-langchainMalware npm · paypal-examples-langchain 2025-07-28 critical10.0 CVE-2025-2828 LangChain Community SSRF vulnerability exists in RequestsToolkit component pip · langchain-community 2025-06-23 critical GHSA-gr63-x6fg-h3wg Malware in auth0-langchain-rag-jsMalware npm · auth0-langchain-rag-js 2025-02-03 critical9.8 CVE-2024-8309 Langchain SQL Injection vulnerability pip · langchain, pip · langchain-community 2024-10-29 critical9.1 CVE-2024-7774 Langchain Path Traversal vulnerability npm · langchain 2024-10-29 critical9.8 CVE-2024-7042 @langchain/community SQL Injection vulnerability npm · @langchain/community 2024-10-29 critical9.8 CVE-2024-46946 langchain_experimental (aka LangChain Experimental) 0.1.17 through 0.3.0 for LangChain allows attackers to execute arbitrary code through sympy.sympify (which … pip · langchain-experimental 2024-09-19 critical8.5 CVE-2024-21513 Versions of the package langchain-experimental from 0.0.15 and before 0.0.21 are vulnerable to Arbitrary Code Execution when retrieving values from the databas… pip · langchain-experimental 2024-07-15 critical9.8 CVE-2024-27444 langchain_experimental (aka LangChain Experimental) in LangChain before 0.1.8 allows an attacker to bypass the CVE-2023-44467 fix and execute arbitrary code vi… pip · langchain-experimental 2024-02-26 critical9.8 CVE-2023-32785 Rejected reason: DO NOT USE THIS CVE RECORD. pip · langchain 2023-10-20 critical9.8 CVE-2023-44467 langchain_experimental vulnerable to arbitrary code execution via PALChain in the python exec method pip · langchain-experimental 2023-10-09 critical9.8 CVE-2023-39631 Langchain vulnerable to arbitrary code execution via the evaluate function in the numexpr library pip · langchain, pip · numexpr 2023-09-01 critical9.8 CVE-2023-36281 langchain vulnerable to arbitrary code execution pip · langchain 2023-08-22 critical9.8 CVE-2023-39659 LangChain vulnerable to arbitrary code execution pip · langchain 2023-08-15 critical9.8 CVE-2023-38896 LangChain vulnerable to arbitrary code execution pip · langchain 2023-08-15 critical9.8 CVE-2023-38860 LangChain vulnerable to arbitrary code execution pip · langchain 2023-08-15 critical9.8 CVE-2023-36095 langchain Code Injection vulnerability pip · langchain 2023-08-05 critical9.8 CVE-2023-36188 langchain vulnerable to arbitrary code execution pip · langchain 2023-07-06 critical9.8 CVE-2023-36258 langchain arbitrary code execution vulnerability pip · langchain 2023-07-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.