NetSight

Security Dashboard

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

Reset
1,025 matching advisories · page 6 of 35Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.1 CVE-2026-62189 OpenClaw versions before 2026.6.9 contain a symlink following vulnerability in the mirror sync feature that allows lower-trust callers to perform actions requi… openclaw · openclaw 2026-07-13 high8.1 CVE-2026-62188 OpenClaw @openclaw/feishu versions 2026.6.6 and earlier contain an incorrect authorization vulnerability in which the Feishu permission tools could ignore per-… openclaw · openclaw\/feishu 2026-07-13 high8.1 CVE-2026-62187 OpenClaw Feishu tools (npm package @openclaw/feishu) in versions <= 2026.6.6 could ignore per-account disablement. openclaw · openclaw\/feishu 2026-07-13 high7.6 CVE-2026-62186 OpenClaw versions before 2026.6.8 contain an authorization bypass vulnerability in OpenAI-compatible HTTP model overrides that allows lower-trust callers to pe… openclaw · openclaw 2026-07-13 high8.7 CVE-2026-62196 OpenClaw versions 2026.3.22 before 2026.6.6 contain an authorization bypass vulnerability where WhatsApp group IDs can satisfy elevated sender allowlists. openclaw · openclaw, OpenClaw · OpenClaw, n/a · OpenClaw 2026-07-13 medium5.3 CVE-2026-15193 A vulnerability was determined in AidanPark openclaw-android up to 0.4.0. AidanPark openclaw-android 2026-07-09 high7.1 CVE-2026-59261 OpenClaw before 2026.5.28 contains a credential exposure vulnerability where workspace dotenv files can override provider credentials. openclaw · openclaw 2026-07-08 high7.2 GHSA-p73f-w79w-jqr5 OpenClaw: Native command authorization could skip owner-command enforcement npm · openclaw 2026-07-02 high7.1 GHSA-77q5-rr5v-x43q OpenClaw: Trusted retry endpoint checks could match hostname prefixes npm · openclaw 2026-07-02 high8.8 GHSA-w5ww-7chg-mxcq OpenClaw: Telegram interactive callbacks could skip commands.allowFrom npm · openclaw 2026-07-02 medium6.3 GHSA-4m3v-q747-pc6h OpenClaw: Mattermost slash token revocation could lag until monitor refresh npm · openclaw 2026-07-02 low3.1 GHSA-3wqp-prf6-2m72 OpenClaw: Feishu dynamic-agent bindings could miss configWrites enforcement npm · openclaw 2026-07-02 medium5.3 GHSA-6c4r-g249-wv3c OpenClaw: Sandboxed session spawn could expose the real workspace path to child prompts npm · openclaw 2026-07-02 high8.3 GHSA-xr4f-mjxj-w6w5 OpenClaw: Non-owner chat senders could issue device-pairing bootstrap codes npm · openclaw 2026-07-02 medium6.5 GHSA-hcm3-8f6r-6xwg OpenClaw: Browser debug/export routes could reuse already-open blocked tabs npm · openclaw 2026-07-02 medium6.8 GHSA-grc3-2j34-p6gm OpenClaw: message.action forwarding could send Gateway credentials to model-supplied loopback URLs npm · openclaw 2026-07-02 critical9.3 GHSA-w4v6-g3wm-w36c OpenClaw: QQBot admin commands could skip DM-only and allowFrom policy npm · openclaw 2026-07-02 high8.8 GHSA-qjpc-qf9m-xwmr OpenClaw: Trusted-proxy Control UI WebSocket accepted client-declared scopes before pairing npm · openclaw 2026-07-02 high8.6 GHSA-c29c-2q9c-pc86 OpenClaw: Slack allowFrom could bind to mutable display names npm · openclaw 2026-07-02 medium5.3 GHSA-cqwv-9qjx-vxw2 OpenClaw: Skill Workshop apply flow could override pending approval npm · openclaw 2026-07-02 medium GHSA-wv26-j37q-2g7p OpenClaw's Slack plugin approvals used the exec approver gate for plugin actions npm · openclaw 2026-07-02 medium6.5 GHSA-p2fh-f5fc-44hr OpenClaw: memory-wiki ingest could read local files with operator.write scope npm · openclaw 2026-07-02 high8.8 GHSA-hw9r-h9mr-4jff OpenClaw: Scoped chat.send route inheritance could bypass admin command scope gates npm · openclaw 2026-07-02 high8.7 GHSA-2j8v-hwgc-x698 OpenClaw: Shell wrapper argv could change between approval and execution npm · Openclaw 2026-07-02 medium6.9 GHSA-qh2f-99mv-mrcf OpenClaw: Bundle MCP loopback could miss its exec denylist on session spawn npm · openclaw 2026-07-02 high8.0 GHSA-xww8-gqvh-92x9 OpenClaw: Exec approval display truncation could hide the command being approved npm · openclaw 2026-07-02 medium6.5 GHSA-9c3v-684m-579c OpenClaw MCP SSE redirects could forward Authorization headers npm · openclaw 2026-07-01 medium6.3 CVE-2026-55249 @rtk-ai/rtk-rewrite transparently rewrites shell commands executed via OpenClaw's exec tool to their RTK equivalents. rtkai · rtk-rewrite 2026-06-23 high8.2 CVE-2026-57495 AgenticMail: Unauthenticated inbound mail triggers bypassPermissions resume of the operator's Claude Code session (bridge-wake) npm · @agenticmail/core, npm · @agenticmail/claudecode, npm · @agenticmail/codex +1 2026-06-18 high8.1 GHSA-vr6h-vxqj-3pjx Duplicate Advisory: Host environment sanitizer missed two Node.js control variables npm · openclaw 2026-06-16

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.