NetSight

Security Dashboard

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

Reset
51 matching advisories · page 2 of 2Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.3 CVE-2026-133627 flowintel contains a log injection vulnerability in its case history (audit log) subsystem. The... flowintel · flowintel 34 hours ago high7.1 CVE-2026-133626 FlowIntel: Resource Exhaustion via Sparse CSV/JSON Table Expansion During File-to-Note Conversion flowintel · flowintel 34 hours ago medium5.3 CVE-2026-133620 Flowintel's template repository subsystem did not adequately constrain file access to the configured repository base directory. flowintel · flowintel 35 hours ago medium6.4 CVE-2026-133613 Flowintel's community data launcher script passes the admin API key as a command-line argument to a child Python helper process. flowintel · flowintel 2 days ago medium4.8 CVE-2026-133178 flowintel allows users with editor-level access to author case and task fields, including aggregated tags. flowintel · flowintel 2 days ago medium5.1 CVE-2026-133157 flowintel contains a CSV injection vulnerability in its audit log CSV export functionality. flowintel · flowintel 2 days ago medium5.3 CVE-2026-133001 FlowIntel contains an authorization flaw in its duplicate alert ingestion logic. When a duplicate... flowintel · flowintel 2 days ago high7.3 CVE-2026-124850 A SQL injection vulnerability exists in a database migration script in flowintel. The migration... flowintel · flowintel 12 days ago medium6.9 CVE-2026-81827 Affected versions of Flowintel incorrectly attempted to validate login email addresses by calling Email(email). 2026-08-27 critical9.1 CVE-2026-81826 Affected versions of Flowintel do not revoke existing authenticated sessions when a user’s password is changed. 2026-08-27 medium5.1 CVE-2026-81820 Affected versions of Flowintel construct timeline HTML using attacker-controllable MISP object fields such as: * object UUID; * object name; * attribute value;… 2026-08-27 medium5.3 CVE-2026-81819 Affected versions of Flowintel expose the /my_assignment/user API endpoint to any authenticated API user. 2026-08-27 high8.6 CVE-2026-81818 Affected versions of Flowintel contain an authorization flaw in the administrative user-edit API. 2026-08-27 high7.2 CVE-2026-81817 Affected versions of Flowintel contain an insecure direct object reference / broken object-level authorization issue across numerous task endpoints. 2026-08-27 medium5.1 CVE-2026-81814 Affected versions of Flowintel render calendar event titles using innerHTML. 2026-08-27 medium5.1 CVE-2026-81753 Affected versions of Flowintel render Mermaid blocks contained in stored case notes without sufficiently neutralizing attacker-controlled markup. 2026-08-27 high7.5 CVE-2026-81743 Affected versions of Flowintel allow the LOG_FILE configuration value to be modified through system settings without restricting it to a filename inside the in… 2026-08-27 high8.6 CVE-2026-81662 Affected versions of Flowintel improperly trust configuration keys supplied to the alerts settings update endpoint. 2026-08-27 high7.1 CVE-2026-81659 Affected versions of Flowintel allow attacker-controlled note content to be processed by Pandoc and XeLaTeX during PDF export in a way that can cause local fil… 2026-08-27 medium6.9 CVE-2026-69075 FlowIntel is affected by a stored cross-site scripting vulnerability through multiple user-controlled or administrator-controlled fields. 2026-08-03 critical9.9 CVE-2026-9813 FlowIntel up to version 3.3.0 contains a server-side request forgery (SSRF) vulnerability in the external reference URL probe functionality in app/case/task.py. flowintel · flowintel 2026-05-28

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.