NetSight

Security Dashboard

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

Reset
45 matching advisories · page 1 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2026-117346 Bitcoin Core through 31.1 is vulnerable to Denial of Service via undo files having no size limit n/a · n/a 23 days ago high7.3 CVE-2026-111210 A vulnerability was determined in bitcoinj up to 0.17. bitcoinj 37 days ago high7.2 CVE-2026-93885 The Cryptocurrency Donation Box – Bitcoin & Crypto Donations plugin for WordPress is vulnerable to Stored Cross-Site Scripting via data_object Parameter in all… 39 days ago high7.5 CVE-2026-66431 Unauthenticated Broken Access Control in Bitcoin Lightning Payment Gateway for WooCommerce (via CLINK) <= 1.0.7 versions. 2026-08-13 high7.5 CVE-2026-44714 The bitcoinj library is a Java implementation of the Bitcoin protocol. maven · org.bitcoinj:bitcoinj-core 2026-05-08 high7.5 CVE-2024-52911 Bitcoin Core through 28.x has a security issue, the details of which are not disclosed. 2026-05-05 high7.5 CVE-2025-46597 Bitcoin Core 0.13.0 through 29.x has an integer overflow. bitcoin · bitcoin_core 2026-03-20 high7.5 CVE-2025-54605 Bitcoin Core through 29.0 allows Uncontrolled Resource Consumption (issue 2 of 2). bitcoin · bitcoin_core 2025-10-28 high7.5 CVE-2025-54604 Bitcoin Core through 29.0 allows Uncontrolled Resource Consumption (issue 1 of 2). bitcoin · bitcoin_core 2025-10-28 high7.1 CVE-2025-26541 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in CodeSolz Bitcoin / AltCoin Payment Gateway for WooCommerc… 2025-03-26 high7.1 CVE-2025-24544 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in dashed-slug.net Bitcoin and Altcoin Wallets wallets allow… Bitcoin and Altcoin Wallets: from n/a through 2025-02-03 high7.5 CVE-2024-52920 Bitcoin Core before 0.20.0 allows remote attackers to cause a denial of service (infinite loop) via a malformed GETDATA message. bitcoin · bitcoin_core 2024-11-18 high7.5 CVE-2024-52916 Bitcoin Core before 0.15.0 allows a denial of service (OOM kill of a daemon process) via a flood of minimum difficulty headers. bitcoin · bitcoin_core 2024-11-18 high7.5 CVE-2024-52915 Bitcoin Core before 0.20.0 allows remote attackers to cause a denial of service (memory consumption) via a crafted INV message. bitcoin · bitcoin_core 2024-11-18 high7.5 CVE-2024-52914 In Bitcoin Core before 0.18.0, a node could be stalled for hours when processing the orphans of a crafted unconfirmed transaction. bitcoin · bitcoin_core 2024-11-18 high7.5 CVE-2024-52912 Bitcoin Core before 0.21.0 allows a network split that is resultant from an integer overflow (calculating the time offset for newly connecting peers) and an ab… bitcoin · bitcoin_core 2024-11-18 high7.5 CVE-2019-25220 Bitcoin Core before 24.0.1 allows remote attackers to cause a denial of service (daemon crash) via a flood of low-difficulty header chains (aka a "Chain Width … bitcoin · bitcoin_core 2024-11-18 high7.4 CVE-2024-38365 btcd did not correctly re-implement Bitcoin Core's "FindAndDelete()" functionality go · github.com/btcsuite/btcd 2024-10-10 high7.5 CVE-2024-35202 Bitcoin Core before 25.0 allows remote attackers to cause a denial of service (blocktxn message-handling assertion and node exit) by including transactions in … bitcoin · bitcoin_core 2024-10-10 high7.5 CVE-2024-44073 Miniscript allows stack consumption rust · miniscript 2024-08-19 high7.5 CVE-2023-39910 The cryptocurrency wallet entropy seeding mechanism used in Libbitcoin Explorer 3.0.0 through 3.6.0 is weak, aka the Milk Sad issue. libbitcoin · libbitcoin_explorer 2023-08-09 high7.5 CVE-2023-37192 Memory management and protection issues in Bitcoin Core v22 allows attackers to modify the stored sending address within the app's memory, potentially allowing… bitcoin · bitcoin_core 2023-07-07 high7.5 CVE-2023-33297 Bitcoin Core before 24.1, when debug mode is not used, allows attackers to cause a denial of service (e.g., CPU consumption) because draining the inventory-to-… bitcoin · bitcoin_core 2023-05-22 high7.1 CVE-2022-47145 Reflected Cross-Site Scripting (XSS) vulnerability in Blockonomics WordPress Bitcoin Payments – Blockonomics plugin <= 3.5.7 versions. blockonomics · blockonomics 2023-03-23 high7.5 CVE-2021-3195 bitcoind in Bitcoin Core through 0.21.0 can create a new file in an arbitrary directory (e.g., outside the ~/.bitcoin directory) via a dumpwallet RPC call. bitcoin · bitcoin_core 2021-01-26 high7.5 CVE-2018-1000893 Bitcoin SV before 0.1.1 allows uncontrolled resource consumption when deserializing transactions. bitcoinsv · bitcoin_sv 2020-12-23 high7.5 CVE-2018-1000892 Bitcoin SV before 0.1.1 allows uncontrolled resource consumption when receiving sendheaders messages. bitcoinsv · bitcoin_sv 2020-12-23 high7.5 CVE-2018-1000891 Bitcoin SV before 0.1.1 allows uncontrolled resource consumption when receiving messages with invalid checksums. bitcoinsv · bitcoin_sv 2020-12-23 high7.5 CVE-2020-14198 Bitcoin Core 0.20.0 allows remote denial of service. bitcoin · bitcoin_core 2020-09-10 high7.5 CVE-2018-17145 Bitcoin Inventory Out-of-Memory Denial-of-Service Attack (CVE-2018-17145) npm · bcoin 2020-09-10

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.