NetSight

Security Dashboard

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

Reset
138 matching advisories · page 2 of 5Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2026-70472 Flowise is a drag & drop user interface to build a customized large language model flow. npm · flowise 2026-08-04 critical9.8 CVE-2026-69264 Prior to 3.1.3, Flowise CSVAgent interpolates an attacker-controlled segment of the csvFile data URI directly into a Python source-code template that is then e… npm · flowise, npm · flowise-components 2026-08-04 high7.1 CVE-2026-70471 Flowise is a drag-and-drop user interface for building customized large language model (LLM) flows. npm · flowise 2026-08-04 critical9.8 CVE-2026-70470 Flowise is a drag & drop user interface to build a customized large language model flow. npm · flowise, npm · flowise-components 2026-08-04 critical9.8 CVE-2026-69263 Flowise: CVE-2025-8943 Patch Bypass: npm_config_yes bypasses MCP environment variable blocklist (Unauthenticated RCE) npm · flowise, npm · flowise-components 2026-08-04 high8.1 CVE-2026-69262 Flowise: `DELETE /api/v1/chatflows/:id` does not validate resource type, allowing `agentflows:delete` and `chatflows:delete` to delete each other’s flow type npm · flowise 2026-08-04 critical9.4 CVE-2026-69259 Flowise is a drag & drop user interface to build a customized large language model flow. npm · flowise, npm · flowise-components 2026-08-04 critical9.1 CVE-2026-69258 Flowise: Unauthenticated Property Injection into Flow Execution Context via Ungated `overrideConfig` Spread in Prediction API npm · flowise 2026-08-04 high8.6 CVE-2026-69257 Flowise is a drag & drop user interface to build a customized large language model flow. npm · flowise 2026-08-04 critical9.4 CVE-2026-69256 Flowise is a drag & drop user interface to build a customized large language model flow. npm · flowise-components, npm · flowise 2026-08-04 critical9.2 CVE-2026-69255 Flowise: CSV Agent Remote Code Execution via Pyodide Code Injection — Root Shell Verified npm · flowise, npm · flowise-components 2026-08-04 critical9.4 CVE-2026-69254 Flowise is a drag & drop user interface to build a customized large language model flow. npm · flowise, npm · flowise-components 2026-08-04 critical9.0 CVE-2026-69253 Flowise is a drag-and-drop user interface for building customized large language model (LLM) flows. npm · flowise, npm · flowise-components 2026-08-04 high8.8 CVE-2026-69252 Flowise: Missing authorization on `/api/v1/files` allows low-privileged API keys to list and delete files across workspaces within the same organization npm · flowise 2026-08-04 critical9.0 CVE-2026-69251 Flowise is a drag & drop user interface to build a customized large language model flow. npm · flowise, npm · flowise-components 2026-08-04 high7.5 CVE-2026-69250 Flowise is a drag & drop user interface to build a customized large language model flow. npm · flowise 2026-08-04 critical9.8 CVE-2026-56271 Flowise before 3.1.0 (affected versions 3.0.13 and earlier) uses weak hardcoded default JWT secrets ('auth_token', 'refresh_token') and default audience and is… flowiseai · flowise 2026-07-12 critical9.1 CVE-2026-56278 Flowise before 3.1.0 (affected versions 3.0.13 and earlier) uses a weak hardcoded default secret ('flowise') for the express-session middleware when the EXPRES… flowiseai · flowise 2026-06-30 medium6.5 CVE-2026-56277 Flowise before 3.1.2 sets Access-Control-Allow-Origin to a hardcoded wildcard (*) on its text-to-speech (TTS) generation endpoint (packages/server/src/controll… flowiseai · flowise 2026-06-30 medium5.0 CVE-2026-58057 Flowise before 3.1.3 validates Custom MCP stdio environment variables against a denylist using a case-sensitive comparison, so on Windows, where environment na… flowiseai · flowise, FlowiseAI · Flowise 2026-06-28 high8.1 CVE-2025-71335 Flowise before 3.0.10 (affected versions 3.0.7 and earlier) fails to invalidate existing sessions and session tokens after a user changes their password. flowiseai · flowise 2026-06-25 critical9.8 CVE-2025-71333 Flowise through 2.2.4 contains an unauthenticated arbitrary file upload vulnerability in the /api/v1/attachments endpoint when storageType is set to local. flowiseai · flowise 2026-06-25 high8.3 CVE-2025-71328 Flowise before 3.0.10 contains an unverified password change vulnerability. flowiseai · flowise 2026-06-25 critical9.1 CVE-2025-71327 Flowise contains an authentication bypass vulnerability in the unprotected /api/v1/account/register endpoint that allows unauthenticated attackers to create us… flowiseai · flowise 2026-06-25 high7.5 CVE-2025-71324 Flowise before 3.0.6 contains an arbitrary file read vulnerability in the chatId parameter of the /api/v1/get-upload-file and /api/v1/openai-assistants-file/do… flowiseai · flowise 2026-06-25 critical9.9 CVE-2026-56274 Flowise before 3.1.2 contains multiple OS command injection vulnerabilities in the Custom MCP Server feature due to incomplete command-flag validation and a re… flowiseai · flowise 2026-06-23 high8.3 CVE-2025-71337 Flowise before 3.0.10 (affected versions 3.0.7 and earlier) contains an unverified email change vulnerability. flowiseai · flowise 2026-06-23 medium6.3 CVE-2026-12821 A vulnerability was determined in FlowiseAI Flowise up to 3.1.2. FlowiseAI Flowise 2026-06-22 medium6.0 CVE-2026-56276 Flowise before 3.1.2 contains a mass assignment vulnerability in the PUT /api/v1/user endpoint that allows authenticated users to directly modify the credentia… FlowiseAI · Flowise 2026-06-20 medium6.9 CVE-2026-56267 Flowise before 3.0.13 contains an information exposure vulnerability in the POST /api/v1/account/forgot-password endpoint that returns full user objects includ… FlowiseAI · Flowise 2026-06-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.