NetSight

Security Dashboard

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

Reset
28 matching advisories · page 1 of 1Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.3 CVE-2026-105856 Payload is a free and open source headless content management system. npm · @payloadcms/db-sqlite, npm · @payloadcms/db-d1-sqlite, npm · @payloadcms/db-postgres +1 46 days ago high6.5 CVE-2026-94483 Next.js is a React framework for building full-stack web applications. npm · next 50 days ago high8.3 CVE-2026-64649 Next.js: Server-Side Request Forgery in Server Actions on custom servers npm · next 2026-07-22 high8.3 CVE-2026-64645 Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname npm · next 2026-07-22 high8.2 CVE-2026-64642 Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale npm · next 2026-07-22 high7.5 CVE-2026-64641 Next.js is a React framework for building full-stack web applications. npm · next 2026-07-22 high7.3 CVE-2026-8768 A vulnerability was found in vercel ai up to 3.0.97. vercel · ai 2026-05-17 high7.8 CVE-2026-46508 Turborepo is a high-performance build system for JavaScript and TypeScript codebases. vercel · turborepo_language_server_protocol 2026-05-15 high7.5 CVE-2026-45109 Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up npm · next 2026-05-11 high7.5 CVE-2026-44579 Next.js vulnerable to Denial of Service via connection exhaustion in applications using Cache Components npm · next 2026-05-11 high8.6 CVE-2026-44578 Next.js vulnerable to server-side request forgery in applications using WebSocket upgrades npm · next 2026-05-11 high7.5 CVE-2026-44575 Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes npm · next 2026-05-11 high8.1 CVE-2026-44574 Next.js has a Middleware / Proxy bypass through dynamic route parameter injection npm · next 2026-05-11 high7.5 CVE-2026-44573 Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n npm · next 2026-05-11 high7.5 CVE-2026-27980 Next.js: Unbounded next/image disk cache growth can exhaust storage npm · next 2026-03-17 high7.5 CVE-2026-27979 Next.js: Unbounded postponed resume buffering can lead to DoS npm · next 2026-03-17 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 high7.5 CVE-2025-49826 Next.JS vulnerability can lead to DoS via cache poisoning npm · next 2025-07-03 high7.5 CVE-2024-51479 Next.js authorization bypass vulnerability npm · next 2024-12-17 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 high7.5 CVE-2024-34350 Next.js Vulnerable to HTTP Request Smuggling npm · next 2024-05-09 high7.5 CVE-2023-46298 Next.js missing cache-control header may lead to CDN caching empty reply npm · next 2023-10-22 high7.5 CVE-2021-43803 Unexpected server crash in Next.js. npm · next 2021-12-07 high7.5 CVE-2021-39178 XSS in Image Optimization API for Next.js npm · next 2021-08-31 high7.5 CVE-2015-8315 Regular Expression Denial of Service in ms npm · ms 2017-01-23

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.