NetSight

Security Dashboard

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

Reset
138 matching advisories · page 4 of 5Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.1 CVE-2026-41270 Flowise: SSRF Protection Bypass via Unprotected Built-in HTTP Modules in Custom Function Sandbox npm · flowise, npm · flowise-components 2026-04-16 high7.1 CVE-2026-41269 Flowise is a drag & drop user interface to build a customized large language model flow. npm · flowise 2026-04-16 critical9.8 CVE-2026-41268 Flowise is a drag & drop user interface to build a customized large language model flow. npm · flowise, npm · flowise-components 2026-04-16 high7.5 CVE-2026-41266 Flowise is a drag & drop user interface to build a customized large language model flow. npm · flowise 2026-04-16 high8.1 CVE-2026-41267 Flowise: Improper Mass Assignment in Account Registration Enables Unauthorized Organization Association npm · flowise 2026-04-16 critical8.8 CVE-2026-41137 Flowise is a drag & drop user interface to build a customized large language model flow. npm · flowise, npm · flowise-components 2026-04-16 high8.8 CVE-2026-41138 Flowise: Remote code execution vulnerability in AirtableAgent.ts caused by lack of input verification when using `Pandas`. npm · flowise, npm · flowise-components 2026-04-16 high7.1 CVE-2026-56275 Flowise before 3.1.0 contains a server-side request forgery vulnerability in the Execute Flow node that allows attackers to bypass security validation by provi… npm · flowise, npm · flowise-components 2026-04-16 critical9.8 CVE-2026-43995 Flowise: SSRF Protection Bypass via Direct node-fetch / axios Usage (Patch Enforcement Failure) npm · flowise, npm · flowise-components 2026-04-16 medium4.6 CVE-2026-56269 Flowise before 3.1.0 (npm package flowise, versions 3.0.13 and earlier) uses a weak hardcoded default value 'Secre$t' for the TOKEN_HASH_SECRET environment var… npm · flowise 2026-04-16 high7.5 CVE-2026-56270 Flowise before 3.1.0 (versions 3.0.13 and earlier) contains a missing authentication vulnerability in the /api/v1/loginmethod endpoint that allows unauthentica… npm · flowise 2026-04-16 critical9.9 CVE-2026-40933 Flowise is a drag & drop user interface to build a customized large language model flow. npm · flowise, npm · flowise-components 2026-04-16 high7.1 CVE-2026-31829 Flowise affected by Server-Side Request Forgery (SSRF) in HTTP Node Leading to Internal Network Access npm · flowise, npm · flowise-components 2026-03-10 critical9.8 CVE-2026-30824 Flowise Missing Authentication on NVIDIA NIM Endpoints npm · flowise 2026-03-06 high8.8 CVE-2026-30823 Flowise has IDOR leading to Account Takeover and Enterprise Feature Bypass via SSO Configuration npm · flowise 2026-03-06 high7.7 CVE-2026-30822 Flowise Allows Mass Assignment in `/api/v1/leads` Endpoint npm · flowise 2026-03-06 critical9.8 CVE-2026-30821 Flowise has Arbitrary File Upload via MIME Spoofing npm · flowise 2026-03-06 high8.7 CVE-2026-30820 Flowise has Authorization Bypass via Spoofed x-request-from Header npm · flowise 2026-03-06 medium4.1 CVE-2026-56272 Flowise before 3.0.13 uses bcrypt with default salt rounds of 5, providing only 32 iterations instead of the OWASP-recommended minimum of 10 rounds. npm · flowise 2026-03-05 critical9.1 GHSA-3g4j-r53p-22wx Duplicate Advisory: FlowiseAI Pre-Auth Arbitrary Code Execution npm · flowise 2025-10-17 critical9.9 CVE-2025-34267 Flowise v3.0.1 < 3.0.8, and 3.0.8 < 3.1.3 with 'ALLOW_BUILTIN_DEP' enabled contain an authenticated remote code execution vulnerability and node VM sandbox esc… npm · flowise 2025-10-14 critical9.9 CVE-2025-61913 Flowise is vulnerable to arbitrary file write through its WriteFileTool npm · flowise, npm · flowise-components, npm · Flowise 2025-10-08 high8.3 CVE-2025-61687 FlowiseAI/Flosise has File Upload vulnerability npm · flowise 2025-10-06 high8.2 GHSA-7rgr-72hp-9wp3 Duplicate Advisory: Flowise is vulnerable to stored XSS via "View Messages" allows credential theft in FlowiseAI admin panel npm · flowise 2025-10-06 high8.2 CVE-2025-29192 Flowise Stored XSS vulnerability through logs in chatbot npm · flowise 2025-10-03 critical9.3 CVE-2025-50538 Flowise is vulnerable to stored XSS via "View Messages" allows credential theft in FlowiseAI admin panel npm · flowise 2025-10-03 critical9.8 CVE-2025-71336 Flowise before 3.0.6 (affected versions 2.2.7-patch.1 and earlier) contains an unsandboxed remote code execution vulnerability in the Custom MCP feature, which… npm · flowise 2025-09-15 critical9.8 CVE-2025-71334 Flowise before 3.0.6 contains an arbitrary file access vulnerability due to missing validation that the chatflowId and chatId parameters are UUIDs or numbers i… npm · flowise 2025-09-15 critical10.0 CVE-2025-59528 Flowise has Remote Code Execution vulnerability npm · flowise 2025-09-15 high7.5 CVE-2025-59527 FlowiseAI/Flowise has Server-Side Request Forgery (SSRF) vulnerability npm · flowise 2025-09-15

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.