NetSight

Security Dashboard

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

Reset
305 matching advisories · page 4 of 11Index updated 8 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.1 CVE-2026-42349 Clerk has an authorization bypass when combining organization, billing, or reverification checks npm · @clerk/shared, npm · @clerk/backend, npm · @clerk/nextjs +14 2026-04-30 medium6.3 CVE-2026-31370 Honor E APP is affected by information leak vulnerability, successful exploitation of this vulnerability may affect service confidentiality. 2026-04-21 medium4.3 CVE-2026-56761 hono before 4.12.14 contains an html injection vulnerability in jsx server-side rendering that allows attackers to inject unintended html by using malformed at… npm · hono 2026-04-16 medium4.8 CVE-2026-39410 Hono is a Web application framework that provides support for any JavaScript runtime. npm · hono 2026-04-08 medium5.3 CVE-2026-39409 Hono is a Web application framework that provides support for any JavaScript runtime. npm · hono 2026-04-08 medium5.3 CVE-2026-56762 Hono before 4.12.12 does not validate cookie names on the write path in the setCookie(), serialize(), and serializeSigned() functions, allowing invalid charact… npm · hono 2026-04-08 high7.5 CVE-2026-39408 Hono is a Web application framework that provides support for any JavaScript runtime. npm · hono 2026-04-08 medium5.3 CVE-2026-39407 Hono is a Web application framework that provides support for any JavaScript runtime. npm · hono 2026-04-08 medium5.3 CVE-2026-39406 @hono/node-server: Middleware bypass via repeated slashes in serveStatic npm · @hono/node-server 2026-04-08 high7.4 CVE-2026-34076 Clerk: SSRF in the opt-in clerkFrontendApiProxy feature may leak secret keys to unintended host npm · @clerk/backend, npm · @clerk/express, npm · @clerk/hono +1 2026-03-27 medium6.5 CVE-2026-35658 OpenClaw before 2026.3.2 contains a filesystem boundary bypass vulnerability in the image tool that fails to honor tools.fs.workspaceOnly restrictions. npm · openclaw 2026-03-26 medium4.8 CVE-2026-56763 Hono before 4.12.7 allows __proto__ key in parseBody with dot option enabled, permitting specially crafted form field names to create objects with __proto__ pr… npm · hono 2026-03-11 high8.1 CVE-2026-22419 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in AncoraThemes Honor honor allows PHP Lo… Honor: from n/a through 2026-03-05 high7.5 CVE-2026-29087 @hono/node-server has authorization bypass for protected static paths via encoded slashes in Serve Static Middleware npm · @hono/node-server 2026-03-04 medium5.4 CVE-2026-29086 Hono Vulnerable to Cookie Attribute Injection via Unsanitized domain and path in setCookie() npm · hono 2026-03-04 medium6.5 CVE-2026-29085 Hono Vulnerable to SSE Control Field Injection via CR/LF in writeSSE() npm · hono 2026-03-04 high7.5 CVE-2026-29045 Hono vulnerable to arbitrary file access via serveStatic vulnerability npm · hono 2026-03-04 high8.9 GHSA-9f72-qcpw-2hxc OpenClaw: Native prompt image auto-load did not honor tools.fs.workspaceOnly in sandboxed runs npm · openclaw 2026-03-03 high8.2 CVE-2026-27700 Hono is Vulnerable to Authentication Bypass by IP Spoofing in AWS Lambda ALB conninfo npm · hono 2026-02-25 low3.7 GHSA-gq3j-xvxp-8hrf Hono added timing comparison hardening in basicAuth and bearerAuth npm · hono 2026-02-19 medium4.7 CVE-2026-24771 Hono vulnerable to XSS through ErrorBoundary component npm · hono 2026-01-27 medium5.3 CVE-2026-24473 Hono has an Arbitrary Key Read in Serve static Middleware (Cloudflare Workers Adapter) npm · hono 2026-01-27 medium5.3 CVE-2026-24472 Hono cache middleware ignores "Cache-Control: private" leading to Web Cache Deception npm · hono 2026-01-27 medium4.8 CVE-2026-24398 Hono IPv4 address validation bypass in IP Restriction Middleware allows IP spoofing npm · hono 2026-01-27 high8.2 CVE-2026-22818 Hono JWK Auth Middleware has JWT algorithm confusion when JWK lacks "alg" (untrusted header.alg fallback) npm · hono 2026-01-13 high8.2 CVE-2026-22817 Hono JWT Middleware's JWT Algorithm Confusion via Unsafe Default (HS256) Allows Token Forgery and Auth Bypass npm · hono 2026-01-13 critical GHSA-qjrq-hrv7-m27w Malware in @trpc-rate-limiter/honoMalware npm · @trpc-rate-limiter/hono 2025-11-24 critical GHSA-9c65-qg9h-c3gr Malware in rce-poc-test-honor-mcpMalware npm · rce-poc-test-honor-mcp 2025-11-07 critical GHSA-4gpw-28rw-46xp Malware in rce-poc-test-honor-devMalware npm · rce-poc-test-honor-dev 2025-11-07 medium4.2 CVE-2025-71381 Hono vulnerable to Vary Header Injection leading to potential CORS Bypass npm · hono 2025-10-24

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.