NetSight

Security Dashboard

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

Reset
104 matching advisories · page 3 of 4Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.3 CVE-2026-27978 Next.js: null origin can bypass Server Actions CSRF checks npm · next 2026-03-17 medium5.4 CVE-2026-27977 Next.js: null origin can bypass dev HMR websocket CSRF checks npm · next 2026-03-17 medium5.3 GHSA-9r75-g2cr-3h76 Vercel Workflow Allows Webhook Creation with Predictable User-Specified Tokens npm · workflow, npm · @workflow/core 2026-03-06 medium5.3 CVE-2026-27118 Cache poisoning in @sveltejs/adapter-vercel npm · @sveltejs/adapter-vercel 2026-02-19 medium5.9 CVE-2025-59472 Next.js has Unbounded Memory Consumption via PPR Resume Endpoint npm · next 2026-01-26 medium5.9 CVE-2025-59471 Next.js self-hosted applications vulnerable to DoS via Image Optimizer remotePatterns configuration npm · next 2026-01-26 high7.5 CVE-2025-67779 Denial of Service Vulnerability in React Server Components npm · react-server-dom-parcel, npm · react-server-dom-turbopack, npm · react-server-dom-webpack 2025-12-12 high7.5 CVE-2025-55184 Denial of Service Vulnerability in React Server Components npm · react-server-dom-parcel, npm · react-server-dom-turbopack, npm · react-server-dom-webpack 2025-12-11 medium5.3 CVE-2025-55183 Source Code Exposure Vulnerability in React Server Components npm · react-server-dom-parcel, npm · react-server-dom-turbopack, npm · react-server-dom-webpack 2025-12-11 critical10.0 CVE-2025-55182 Meta React Server Components Remote Code Execution VulnerabilityExploited npm · react-server-dom-webpack, npm · react-server-dom-turbopack, npm · react-server-dom-parcel 2025-12-03 critical GHSA-f422-9v6v-3mm2 Malware in n8n-nodes-vercel-ai-sdkMalware npm · n8n-nodes-vercel-ai-sdk 2025-11-24 low3.7 CVE-2025-48985 Vercel’s AI SDK's filetype whitelists can be bypassed when uploading files npm · ai 2025-11-07 critical GHSA-52hh-6hxr-wp2p Malware in vercel-v0Malware npm · vercel-v0 2025-10-09 medium6.2 CVE-2025-57752 Next.js Affected by Cache Key Confusion for Image Optimization API Routes npm · next 2025-08-29 medium4.3 CVE-2025-55173 Next.js Content Injection Vulnerability for Image Optimization npm · next 2025-08-29 medium6.5 CVE-2025-57822 Next.js Improper Middleware Redirect Handling Leads to SSRF npm · next 2025-08-29 medium4.3 CVE-2025-7074 A vulnerability classified as problematic has been found in vercel hyper up to 3.4.1. vercel · hyper 2025-07-05 high7.5 CVE-2025-49826 Next.JS vulnerability can lead to DoS via cache poisoning npm · next 2025-07-03 low3.7 CVE-2025-49005 Next.js has a Cache poisoning vulnerability due to omission of the Vary header npm · next 2025-07-03 medium4.3 CVE-2025-48068 Information exposure in Next.js dev server due to lack of origin verification npm · next 2025-05-28 low3.7 CVE-2025-32421 Next.js Race Condition to Cache Poisoning npm · next 2025-05-14 medium6.5 CVE-2025-46332 Information Disclosure via Flags override link npm · flags, npm · @vercel/flags 2025-05-02 medium5.9 CVE-2025-30218 Next.js may leak x-middleware-subrequest-id to external hosts npm · next 2025-04-02 critical9.1 CVE-2025-29927 Authorization Bypass in Next.js Middleware npm · next 2025-03-21 medium5.3 CVE-2024-56332 Next.js Allows a Denial of Service (DoS) with Server Actions npm · next 2025-01-03 high7.5 CVE-2024-51479 Next.js authorization bypass vulnerability npm · next 2024-12-17 medium5.9 CVE-2024-47831 Denial of Service condition in Next.js image optimization npm · next 2024-10-14 high7.5 CVE-2024-46982 Next.js Cache Poisoning npm · next 2024-09-17 high7.5 CVE-2024-39693 Next.js Denial of Service (DoS) condition npm · next 2024-07-10 high7.5 CVE-2024-34351 Next.js Server-Side Request Forgery in Server Actions npm · next 2024-05-09

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.