NetSight

Security Dashboard

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

Reset
481 matching advisories · page 9 of 17Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.9 GHSA-98ch-45wp-ch47 OpenClaw: Windows-compatible env override keys could bypass system.run approval binding npm · openclaw 2026-04-07 medium4.3 CVE-2026-41339 OpenClaw before 2026.4.2 exposes configPath and stateDir metadata in Gateway connect success snapshots to non-admin authenticated clients. npm · openclaw 2026-04-07 medium5.4 CVE-2026-41298 OpenClaw before 2026.4.2 fails to enforce write scopes on the POST /sessions/:sessionKey/kill endpoint in identity-bearing HTTP modes. npm · openclaw 2026-04-07 medium4.6 CVE-2026-41398 OpenClaw before 2026.4.2 contains an improper access control vulnerability in the iOS A2UI bridge that treats generic local-network pages as trusted origins. npm · openclaw 2026-04-07 medium6.9 GHSA-846p-hgpv-vphc OpenClaw: QQ Bot structured payloads could read arbitrary local files npm · openclaw 2026-04-07 medium5.3 CVE-2026-41346 OpenClaw 2026.2.26 before 2026.3.31 enforces pending pairing-request caps per channel file instead of per account, allowing attackers to exhaust the shared pen… npm · openclaw 2026-04-07 medium5.3 CVE-2026-41301 OpenClaw versions 2026.3.22 before 2026.3.31 contain a signature verification bypass vulnerability in the Nostr DM ingress path that allows pairing challenges … npm · openclaw 2026-04-07 medium6.7 CVE-2026-41392 OpenClaw before 2026.3.31 contains an exec allowlist bypass vulnerability allowing attackers to inherit allowlist trust via shell init-file wrapper invocations. npm · openclaw 2026-04-07 medium6.3 GHSA-fwjq-xwfj-gv75 OpenClaw: `session_status` still bypasses configured `tools.sessions.visibility` for unsandboxed invocations npm · openclaw 2026-04-07 medium4.3 CVE-2026-41408 OpenClaw before 2026.3.31 contains a resource exhaustion vulnerability in media downloads that bypasses core safety limits for file size, count, and cleanup op… npm · openclaw 2026-04-07 medium6.5 CVE-2026-41375 OpenClaw before 2026.3.28 contains an authorization bypass vulnerability in the /phone arm and /phone disarm endpoints that fails to properly enforce operator.… npm · openclaw 2026-04-07 medium5.3 GHSA-ch86-pxr9-j9h9 Duplicate Advisory: OpenClaw: Gemini OAuth exposed the PKCE verifier through the OAuth state parameter npm · openclaw 2026-04-03 medium5.4 CVE-2026-41382 OpenClaw before 2026.3.31 contains an authorization bypass vulnerability in Discord voice ingress that allows attackers to bypass channel and member allowlist … npm · openclaw 2026-04-03 medium5.4 CVE-2026-41341 OpenClaw before 2026.3.31 contains a logic error in Discord component interaction routing that misclassifies group direct messages as direct messages in extens… npm · openclaw 2026-04-03 medium6.5 CVE-2026-41300 OpenClaw before 2026.3.31 contains a trust-decline vulnerability that preserves attacker-discovered endpoints in remote onboarding flows. npm · openclaw 2026-04-03 medium4.0 CVE-2026-41403 OpenClaw before 2026.3.31 misclassifies proxied remote requests as loopback connections in the diffs viewer when allowRemoteViewer is disabled, allowing unauth… npm · openclaw 2026-04-03 medium5.4 CVE-2026-41348 OpenClaw before 2026.3.31 contains an authorization bypass vulnerability in Discord slash command and autocomplete paths that fail to enforce group DM channel … npm · openclaw 2026-04-03 medium6.3 GHSA-f693-58pc-2gfr OpenClaw: Telegram legacy allowFrom migration fans default-account trust into all named accounts npm · openclaw 2026-04-03 medium6.5 CVE-2026-41388 OpenClaw before 2026.3.31 contains a configuration management vulnerability where startup migration treats empty-array settings as missing values. npm · openclaw 2026-04-03 medium5.4 CVE-2026-41381 OpenClaw before 2026.3.31 contains an access control bypass vulnerability in the Discord voice manager that allows attackers to bypass channel-level member acc… npm · openclaw 2026-04-03 medium5.3 CVE-2026-41331 OpenClaw before 2026.3.31 contains a resource consumption vulnerability in Telegram audio preflight transcription that allows unauthorized group senders to tri… npm · openclaw 2026-04-03 medium5.3 CVE-2026-41400 OpenClaw before 2026.3.31 contains an incomplete fix for CVE-2026-32062 where the voice-call component parses large WebSocket frames before start validation. npm · openclaw 2026-04-03 medium5.4 CVE-2026-41356 OpenClaw: Gateway `device.token.rotate` does not terminate active WebSocket sessions after credential rotation npm · openclaw 2026-04-03 medium3.7 CVE-2026-41333 OpenClaw before 2026.3.31 contains an authentication rate limiting bypass vulnerability that allows attackers to circumvent shared authentication protections u… npm · openclaw 2026-04-03 medium5.3 GHSA-58q2-7r52-jq62 OpenClaw: Path traversal via inbound channel attachment path in ACP dispatch allows arbitrary file read npm · openclaw 2026-04-03 medium5.3 CVE-2026-41335 OpenClaw before 2026.3.31 contains an information disclosure vulnerability in the Control Interface bootstrap JSON that exposes version and assistant agent ide… npm · openclaw 2026-04-03 medium5.8 GHSA-rm5c-4rmf-vvhw OpenClaw: Sandbox file operations use check-then-act, bypassing fd-based TOCTOU defenses npm · openclaw 2026-04-03 medium6.9 GHSA-w85g-3h6x-4xh2 OpenClaw: Image pixel-limit guard can fail open on sips and allow decompression-bomb DoS npm · openclaw 2026-04-03 medium5.3 CVE-2026-41351 OpenClaw before 2026.3.31 contains a replay detection bypass vulnerability in webhook signature handling that treats Base64 and Base64URL encoded signatures as… npm · openclaw 2026-04-03 medium4.4 CVE-2026-41330 OpenClaw before 2026.3.31 contains an environment variable override vulnerability in host exec policy that fails to properly enforce proxy, TLS, Docker, and Gi… npm · openclaw 2026-04-03

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.