NetSight

Security Dashboard

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

Reset
215 matching advisories · page 6 of 8Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.7 CVE-2026-47394 PraisonAI vulnerable to unauthenticated arbitrary file read via MCP workflow.show, workflow.validate, deploy.validate pip · PraisonAI 2026-05-29 critical9.9 CVE-2026-47392 PraisonAI vulnerable to sandbox escape via `print.__self__` builtins module leak in `execute_code` (subprocess mode) pip · praisonaiagents, pip · PraisonAI 2026-05-29 medium5.5 CVE-2026-47395 PraisonAI CLI automatically resolves @url mentions in prompt text and can read loopback URLs into model context pip · praisonaiagents, pip · PraisonAI 2026-05-29 critical9.8 CVE-2026-47393 PraisonAI `deploy --type api` emits a Flask server with authentication disabled by default pip · PraisonAI 2026-05-29 critical9.8 CVE-2026-47396 PraisonAI call server exposes unauthenticated agent listing, invocation, and deletion when CALL_SERVER_TOKEN is unset pip · PraisonAI 2026-05-29 medium5.5 CVE-2026-47390 PraisonAI spider_tools SSRF protection bypass via alternate loopback host encodings pip · praisonaiagents, pip · PraisonAI 2026-05-29 high8.1 CVE-2026-47398 PraisonAI: Arbitrary code execution via unguarded `spec.loader.exec_module` in `agents_generator.py` - sibling of CVE-2026-44334 pip · PraisonAI 2026-05-29 high7.5 CVE-2026-44340 PraisonAI's symlink-extraction bypass of `_safe_extractall` writes outside `dest_dir` pip · PraisonAI 2026-05-08 high8.6 CVE-2026-44339 PraisonAI has unsafe tool resolution in `ToolExecutionMixin.execute_tool`: undeclared `__main__` callables execute pip · praisonaiagents, pip · PraisonAI 2026-05-08 high7.3 CVE-2026-44338 PraisonAI ships and generates a legacy API server with authentication disabled by default, allowing unauthenticated workflow execution pip · PraisonAI 2026-05-08 medium6.3 CVE-2026-44337 PraisonAI knowledge-store backends interpolate unvalidated collection names into SQL and CQL queries pip · PraisonAI 2026-05-08 critical9.6 CVE-2026-44336 PraisonAI MCP `tools/call` path-traversal => RCE via Python `.pth` injection pip · PraisonAI 2026-05-08 high8.4 CVE-2026-44334 PraisonAI has unauthenticated RCE via `tool_override.py` (CVE-2026-40287 patch bypass) pip · praisonai 2026-05-06 critical9.8 CVE-2026-44335 PraisonAI is a multi-agent teams system. pip · praisonaiagents 2026-05-06 high8.1 CVE-2026-41496 PraisonAI: SQL Injection via unvalidated `table_prefix` in 9 conversation store backends (incomplete fix for CVE-2026-40315) pip · praisonai, pip · praisonaiagents 2026-04-17 critical9.8 CVE-2026-41497 PraisonAI has an incomplete fix for CVE-2026-34935 - OS Command Injection pip · praisonai 2026-04-17 critical9.1 CVE-2026-40313 PraisonAI is a multi-agent teams system. praison · praisonai 2026-04-14 critical9.1 CVE-2026-40289 PraisonAI Browser Server allows unauthenticated WebSocket clients to hijack connected extension sessions pip · praisonaiagents, pip · PraisonAI 2026-04-10 critical9.8 CVE-2026-40288 PraisonAI has critical RCE via `type: job` workflow YAML pip · praisonaiagents, pip · PraisonAI 2026-04-10 high8.4 CVE-2026-40287 PraisonAI Vulnerable to RCE via Automatic tools.py Import pip · praisonaiagents, pip · PraisonAI 2026-04-10 critical9.8 CVE-2026-40315 PraisonAI: SQLiteConversationStore didn't validate table_prefix when constructing SQL queries pip · PraisonAI 2026-04-10 medium6.8 CVE-2026-56074 PraisonAI before 1.5.128 caches tool approval decisions by tool name only, not by invocation arguments, allowing subsequent execute_command calls to bypass app… pip · praisonai, pip · praisonaiagents 2026-04-10 high8.1 GHSA-x462-jjpc-q4q4 PraisonAI: Cross-Origin Agent Execution via Hardcoded Wildcard CORS and Missing Authentication on AGUI Endpoint pip · praisonaiagents 2026-04-10 high8.8 GHSA-qwgj-rrpj-75xm PraisonAI: Hardcoded `approval_mode="auto"` in Chainlit UI Overrides Administrator Configuration, Enabling Unapproved Shell Command Execution pip · PraisonAI 2026-04-10 high7.1 CVE-2026-40160 PraisonAIAgents: SSRF via unvalidated URL in `web_crawl` httpx fallback pip · praisonaiagents 2026-04-10 medium5.5 CVE-2026-40159 PraisonAI Vulnerable to Sensitive Environment Variable Exposure via Untrusted MCP Subprocess Execution pip · PraisonAI 2026-04-10 high8.6 CVE-2026-40158 PraisonAI Vulnerable to Code Injection and Protection Mechanism Failure pip · PraisonAI 2026-04-10 critical9.4 CVE-2026-40157 PraisonAI vulnerable to arbitrary file write via path traversal in `praisonai recipe unpack` pip · PraisonAI 2026-04-10 high7.8 CVE-2026-40156 PraisonAI Vulnerable to Implicit Execution of Arbitrary Code via Automatic `tools.py` Loading pip · praisonai 2026-04-10 critical9.3 CVE-2026-40154 PraisonAI Vulnerable Untrusted Remote Template Code Execution pip · PraisonAI 2026-04-09

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.