NetSight

Security Dashboard

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

Reset
121 matching advisories · page 2 of 5Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.8 CVE-2026-61433 PraisonAI before 4.6.78 fails to safely encode deployment configuration values when generating Python source code for API servers. pip · praisonai 2026-07-15 high8.5 CVE-2026-61430 PraisonAI before 1.6.78 contains a server-side request forgery vulnerability in the web_crawl tool that validates hostnames at check time but re-resolves them … pip · praisonaiagents 2026-07-15 high7.3 CVE-2026-61427 PraisonAI before 4.6.78 exposes the MCP HTTP-stream transport without authentication by default: the CLI --api-key option defaults to None, and the server only… pip · praisonai 2026-07-15 high7.5 CVE-2026-60085 PraisonAI before 4.6.78 contains an unenforced security policy vulnerability in the default Subprocess Sandbox backend where blocked_commands, blocked_paths, b… pip · praisonai 2026-07-15 high7.1 GHSA-f996-h3c6-gcwg Duplicate Advisory: PraisonAI: Platform member PATCH routes allow owner resource rewrites and project lead reassignment delete bypass pip · praisonai-platform 2026-07-11 high7.5 GHSA-5r2q-3wg3-57m2 Duplicate Advisory: PraisonAI: Prompt Injection Defense Bypassed for HIGH-Level Threats pip · praisonai 2026-07-11 high8.5 GHSA-rc3q-9pxg-3jhr Duplicate Advisory: PraisonAI: Crawl4AI/Chromium backend is also affected by the `web_crawl` SSRF validation bypass pip · praisonaiagents 2026-07-11 high8.6 GHSA-g3pq-3vvx-36w6 Duplicate Advisory: PraisonAI: AgentOS defaults to network-exposed no-auth mode, allowing unauthenticated agent invocation and instruction disclosure npm · praisonai 2026-07-11 high7.1 CVE-2026-61442 PraisonAI Platform (praisonai-platform) before 0.1.9 fails to enforce owner/admin authorization on the PATCH routes for projects, issues, and agents, which onl… pip · praisonai-platform 2026-07-11 high7.5 CVE-2026-61439 PraisonAI versions before 4.6.78 contain a prompt injection defense misconfiguration where the block threshold defaults to CRITICAL severity, allowing HIGH-lev… pip · PraisonAI 2026-07-11 high8.5 CVE-2026-61429 PraisonAI versions before 1.6.78 contain a server-side request forgery vulnerability in the Crawl4AI/Chromium backend that allows attackers to bypass SSRF vali… pip · praisonaiagents 2026-07-11 high7.3 CVE-2026-61428 PraisonAI AgentMail versions before 4.6.78 lack signature verification in webhook mode, allowing unauthenticated attackers to inject messages with spoofed send… pip · praisonai 2026-07-11 high8.6 CVE-2026-61426 PraisonAI before 1.7.3 contains an insecure default configuration that binds to all interfaces with no API key requirement and wildcard CORS. npm · praisonai 2026-07-11 high8.8 GHSA-wrw8-384c-cg76 Duplicate Advisory: PraisonAI: Shell command allowlist bypass via find -exec built-in action pip · PraisonAI 2026-07-10 high7.8 GHSA-c6pq-cprj-62fw Duplicate Advisory: PraisonAI: Unsafe Dynamic Module Loading Leads to Arbitrary Code Execution via tools.py in AgentFlow pip · praisonaiagents 2026-07-10 high7.8 CVE-2026-61437 PraisonAI (pip package praisonaiagents) before 1.6.78 contains an unsafe dynamic module loading vulnerability in AgentFlow._resolve_pydantic_class (src/praison… pip · praisonaiagents 2026-07-10 high8.8 CVE-2026-61434 PraisonAI versions before 4.6.78 contain an allowlist bypass vulnerability in shell command execution that allows attackers to execute restricted commands via … pip · praisonai 2026-07-10 high7.2 CVE-2026-60091 PraisonAI before 4.6.78 contains an unauthenticated server-side request forgery vulnerability in the Jobs API /api/v1/runs endpoint. pip · praisonai 2026-07-10 high7.1 CVE-2026-56077 PraisonAI before 1.5.115 contains an information disclosure vulnerability in the MultiAgentLedger component that allows attackers to access sensitive data by r… mervinpraison · PraisonAI 2026-06-18 high8.6 CVE-2026-56076 PraisonAI before 1.5.128 contains a cross-origin agent execution vulnerability in the AGUI endpoint that allows remote attackers to trigger arbitrary agent exe… mervinpraison · PraisonAI 2026-06-18 high8.7 CVE-2026-56075 PraisonAI before 4.5.128 contains an arbitrary shell command execution vulnerability where the UI modules hardcode approval_mode to auto, overriding administra… mervinpraison · PraisonAI 2026-06-18 high8.8 CVE-2026-57144 PraisonAI SandlockSandbox falls back to unrestricted subprocess execution when Landlock is unavailable pip · praisonai 2026-06-18 high8.2 CVE-2026-57132 PraisonAI: PRAISONAI_CALL_AUTH=disabled environment variable unconditionally disables authentication pip · praisonai 2026-06-18 high8.8 CVE-2026-57143 PraisonAI: Server-Side Request Forgery (SSRF) in SearxNG / search_web tools via attacker-controlled searxng_url parameter pip · praisonaiagents 2026-06-18 high7.5 CVE-2026-57146 PraisonAI A2U incomplete authentication fix leaves current serve command unauthenticated by default pip · praisonai 2026-06-18 high7.8 CVE-2026-57142 PraisonAI recipe workflow policy can be bypassed by declaring and YAML-approving dangerous tools outside TEMPLATE.yaml pip · praisonai 2026-06-18 high8.8 CVE-2026-57133 npm PraisonAI utility shell safe-command wrapper allowlist bypass via shell chaining npm · praisonai 2026-06-18 high8.8 CVE-2026-57137 npm PraisonAI AgentLoop onToolCall approval runs after tool execution npm · praisonai 2026-06-18 high8.8 CVE-2026-57136 npm PraisonAI SandboxExecutor allowedCommands bypass via shell chaining npm · praisonai 2026-06-18 high7.6 CVE-2026-57135 npm PraisonAI SandboxExecutor network-isolated mode does not block non-proxy-aware network clients npm · praisonai 2026-06-18

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.