NetSight

Security Dashboard

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

Reset
481 matching advisories · page 8 of 17Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium7.3 GHSA-p6j4-wvmc-vx2h Duplicate Advisory: OpenClaw: Tlon cite expansion happens before channel and DM authorization is complete npm · openclaw 2026-04-10 medium4.8 GHSA-59xc-5v89-r7pr Duplicate Advisory: OpenClaw: Synology Chat Webhook Pre-Auth Rate-Limit Bypass Enables Brute-Force Guessing of Webhook Token npm · openclaw 2026-04-10 medium7.1 GHSA-pmf3-2q63-jmp6 Duplicate Advisory: OpenClaw: Symlink Traversal via IDENTITY.md appendFile in agents.create/update (Incomplete Fix for CVE-2026-32013) npm · openclaw 2026-04-10 medium8.1 GHSA-m5jp-p3r5-mfqp Duplicate Advisory: OpenClaw: Gateway Plugin Subagent Fallback `deleteSession` Uses Synthetic `operator.admin` npm · openclaw 2026-04-10 medium5.3 GHSA-hm63-vwj4-mj2q Duplicate Advisory: OpenClaw: Remote media error responses could trigger unbounded memory allocation before failure npm · openclaw 2026-04-10 medium5.3 GHSA-8f9r-gr6r-x63q Duplicate Advisory: OpenClaw: Feishu webhook reads and parses unauthenticated request bodies before signature validation npm · openclaw 2026-04-10 medium5.1 GHSA-9gvx-vj57-vqqx Duplicate Advisory: OpenClaw: Gateway Canvas local-direct requests bypass Canvas HTTP and WebSocket authentication npm · openclaw 2026-04-10 medium4.8 GHSA-g8mc-c5f2-mqg7 Duplicate Advisory: OpenClaw Bypasses DM Policy Separation via Synology Chat Webhook Path Collision npm · openclaw 2026-04-10 medium4.8 GHSA-r4c2-gq3j-7rpj Duplicate Advisory: OpenClaw: Telegram Webhook Missing Guess Rate Limiting Enables Brute-Force Guessing of Weak Webhook Secret npm · openclaw 2026-04-10 medium5.9 GHSA-hgwr-wr8h-rxm7 Duplicate Advisory: OpenClaw: Google Chat app-url webhook auth accepted non-deployment add-on principals npm · openclaw 2026-04-10 medium4.8 GHSA-rc8f-r29c-chr6 Duplicate Advisory: OpenClaw: BlueBubbles Webhook Missing Rate Limiting Enables Brute-Force Password Guessing npm · openclaw 2026-04-10 medium6.5 CVE-2026-35644 OpenClaw before 2026.3.22 contains an information disclosure vulnerability that allows attackers with operator.read scope to expose credentials embedded in cha… openclaw · openclaw 2026-04-09 medium4.3 CVE-2026-35642 OpenClaw before 2026.3.25 contains an authorization bypass vulnerability where group reaction events bypass the requireMention access control mechanism. openclaw · openclaw 2026-04-09 medium6.5 CVE-2026-35636 OpenClaw versions 2026.3.11 through 2026.3.24 contain a session isolation bypass vulnerability where session_status resolves sessionId to canonical session key… openclaw · openclaw 2026-04-09 medium6.5 CVE-2026-35631 OpenClaw before 2026.3.22 fails to enforce operator.admin scope on mutating internal ACP chat commands, allowing unauthorized modifications. openclaw · openclaw 2026-04-09 medium5.3 CVE-2026-41915 OpenClaw before 2026.4.8 fails to remove git plumbing environment variables from the execution environment before host exec operations. npm · openclaw 2026-04-09 medium4.3 CVE-2026-42420 OpenClaw before 2026.4.8 contains improper input validation in base64 decode paths that allocate memory before enforcing decoded-size limits. npm · openclaw 2026-04-09 medium5.9 GHSA-w9j9-w4cp-6wgr OpenClaw Host-Exec Environment Variable Injection npm · openclaw 2026-04-09 medium6.5 CVE-2026-42430 OpenClaw before 2026.4.8 contains a server-side request forgery vulnerability in Playwright redirect handling that allows attackers to bypass strict SSRF check… npm · openclaw 2026-04-09 medium6.5 CVE-2026-41911 OpenClaw before 2026.4.8 contains a filesystem policy bypass vulnerability in docx upload processing that allows local file reads outside workspace boundaries. npm · openclaw 2026-04-09 medium5.4 CVE-2026-42421 OpenClaw before 2026.4.8 contains a session management vulnerability where existing WebSocket sessions survive shared gateway token rotation. npm · openclaw 2026-04-09 medium4.3 CVE-2026-41910 OpenClaw before 2026.4.8 omits owner-only enforcement for cross-channel allowlist writes in the /allowlist endpoint. npm · openclaw 2026-04-09 medium5.4 CVE-2026-41916 OpenClaw before 2026.4.8 contains an authentication state management vulnerability where the resolvedAuth closure becomes stale after configuration reload. npm · openclaw 2026-04-09 medium5.7 CVE-2026-42424 OpenClaw before 2026.4.8 treats shared reply MEDIA paths as trusted, allowing crafted references to trigger cross-channel local file exfiltration. npm · openclaw 2026-04-09 medium CVE-2026-39398 openclaw-claude-bridge: sandbox is not effective - `--allowed-tools ""` does not restrict available tools npm · openclaw-claude-bridge 2026-04-08 medium5.7 CVE-2026-40045 OpenClaw before 2026.4.2 accepts non-loopback cleartext ws:// gateway endpoints and transmits stored gateway credentials over unencrypted connections. npm · openclaw 2026-04-07 medium3.7 CVE-2026-41407 OpenClaw before 2026.4.2 contains a timing side channel vulnerability in shared-secret comparison call sites that use early length-mismatch checks instead of f… npm · openclaw 2026-04-07 medium6.3 CVE-2026-41354 OpenClaw before 2026.4.2 contains an insufficient scope vulnerability in Zalo webhook replay dedupe keys that allows legitimate events from different conversat… npm · openclaw 2026-04-07 medium5.8 CVE-2026-41372 OpenClaw before 2026.4.2 fails to normalize trailing-dot localhost hosts in remote CDP discovery responses, allowing bypass of loopback protections. npm · openclaw 2026-04-07 medium6.9 GHSA-w6wx-jq6j-6mcj OpenClaw: pnpm dlx approvals did not bind local script operands npm · openclaw 2026-04-07

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.