NetSight

Security Dashboard

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

Reset
142 matching advisories · page 3 of 5Index updated 12 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.7 CVE-2025-7054 quiche connection ID retirement can trigger an infinite loop rust · quiche 2025-08-07 low3.7 GHSA-522r-9946-fw43 Duplicate Advisory: CIRCL-Fourq: Missing and wrong validation can lead to incorrect results go · github.com/cloudflare/circl 2025-08-06 medium6.9 CVE-2025-59427 Cloudflare Vite plugin exposes secrets over the built-in dev server npm · @cloudflare/vite-plugin 2025-07-08 high7.5 CVE-2025-4821 Impact Cloudflare quiche was discovered to be vulnerable to incorrect congestion window growth, which could cause it to send data at a rate faster than the pat… cloudflare · quiche 2025-06-18 medium5.3 CVE-2025-4820 Impact Cloudflare quiche was discovered to be vulnerable to incorrect congestion window growth, which could cause it to send data at a rate faster than the pat… cloudflare · quiche 2025-06-18 critical9.1 CVE-2025-6087 OpenNext for Cloudflare (opennextjs-cloudflare) has a SSRF vulnerability via /_next/image endpoint npm · @opennextjs/cloudflare 2025-06-16 low3.7 CVE-2025-8556 A flaw was found in CIRCL's implementation of the FourQ elliptic curve. go · github.com/cloudflare/circl 2025-06-10 high7.4 CVE-2025-4366 Pingora has a Request Smuggling Vulnerability rust · pingora-core 2025-05-22 medium5.3 GHSA-vh4h-fvqf-q9wv Duplicate Advisory: @cloudflare/workers-oauth-provider PKCE bypass via downgrade attack npm · @cloudflare/workers-oauth-provider 2025-05-01 medium6.0 GHSA-7cp4-jw97-3rc2 Duplicate Advisory: @cloudflare/workers-oauth-provider missing validation of redirect_uri on authorize endpoint npm · @cloudflare/workers-oauth-provider 2025-05-01 critical9.8 CVE-2025-4144 @cloudflare/workers-oauth-provider PKCE bypass via downgrade attack npm · @cloudflare/workers-oauth-provider 2025-05-01 medium6.0 CVE-2025-4143 @cloudflare/workers-oauth-provider missing validation of redirect_uri on authorize endpoint npm · @cloudflare/workers-oauth-provider 2025-05-01 critical GHSA-qxq3-jpfr-jw4v Malware in cloudflare-workers-chatgpt-plugin-exampleMalware npm · cloudflare-workers-chatgpt-plugin-example 2025-02-03 high7.1 CVE-2025-22332 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in shanaver CloudFlare(R) Cache Purge cloudflare-cache-purge… CloudFlare(R) Cache Purge: from n/a through 2025-01-31 high7.1 CVE-2025-0651 Improper Privilege Management vulnerability in Cloudflare WARP on Windows allows File Manipulation. cloudflare · warp 2025-01-22 critical GHSA-v637-xx75-2fj6 Malware in code.cloudflare.ajaxMalware npm · code.cloudflare.ajax 2024-06-11 critical GHSA-qmj4-r9pg-cw88 Malware in code.cloudflare.comMalware npm · code.cloudflare.com 2024-06-11 high7.1 CVE-2024-27968 Cross-Site Request Forgery (CSRF) vulnerability in Optimole Super Page Cache for Cloudflare allows Stored XSS.This issue affects Super Page Cache for Cloudflar… optimole · super_page_cache 2024-03-21 medium5.9 CVE-2024-1765 quiche vulnerable to unlimited resource allocation by QUIC CRYPTO frames flooding rust · quiche 2024-03-12 low3.7 CVE-2024-1410 quiche vulnerable to unbounded storage of information related to connection ID retirement rust · quiche 2024-03-12 high8.1 CVE-2024-0212 The Cloudflare Wordpress plugin was found to be vulnerable to improper authentication. cloudflare · cloudflare 2024-01-29 critical GHSA-cf45-w86j-cc99 Malware in cloudflare-docs-themeMalware npm · cloudflare-docs-theme 2024-01-11 high GHSA-9763-4f94-gfch CIRCL's Kyber: timing side-channel (kyberslash2) go · github.com/cloudflare/circl 2024-01-08 medium4.0 CVE-2023-6992 Cloudflare version of zlib library was found to be vulnerable to memory corruption issues affecting the deflation algorithm implementation (deflate.c). cloudflare · zlib 2024-01-04 critical9.3 CVE-2023-7080 Arbitrary remote code execution within `wrangler dev` Workers sandbox npm · wrangler 2023-12-29 medium6.9 CVE-2023-7079 Arbitrary remote file read in Wrangler dev server npm · wrangler 2023-12-29 high7.5 CVE-2023-7078 Miniflare vulnerable to Server-Side Request Forgery (SSRF) npm · miniflare 2023-12-29 medium5.3 CVE-2023-6193 Unbounded queuing of path validation messages in cloudflare-quiche rust · quiche 2023-12-12 medium5.3 CVE-2023-6180 tokio-boring vulnerable to resource exhaustion via memory leak rust · tokio-boring 2023-12-05 medium6.4 CVE-2023-5135 The Simple Cloudflare Turnstile plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'gravity-simple-turnstile' shortcode in versions up to, a… replywp · simple_cloudfare_turnstile 2023-09-27

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.