NetSight

Security Dashboard

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

Reset
145 matching advisories · page 2 of 5Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-73qx-22f2-c6g7 Malicious code in BitcoinLib.Net (NuGet)Malware nuget · BitcoinLib.Net, nuget · BitcoinLib.Net, nuget · BitcoinLib.Net +7 2026-07-20 critical GHSA-9gjc-2546-5v7h Malicious code in bitcoincore (NuGet)Malware nuget · bitcoincore, nuget · bitcoincore, nuget · bitcoincore +4 2026-07-20 critical GHSA-298f-fc6x-x47v Malicious code in Blockcore.Networks.Bitcoin.Bc (NuGet)Malware nuget · Blockcore.Networks.Bitcoin.Bc, nuget · Blockcore.Networks.Bitcoin.Bc, nuget · Blockcore.Networks.Bitcoin.Bc 2026-07-20 critical GHSA-wj6f-55q8-2h73 Malicious code in Autarkysoft.Bitcoin.Net (NuGet)Malware nuget · Autarkysoft.Bitcoin.Net, nuget · Autarkysoft.Bitcoin.Net, nuget · Autarkysoft.Bitcoin.Net 2026-07-20 medium4.0 CVE-2023-7346 Ledger Bitcoin app versions 2.1.0 and 2.1.1 contain an address derivation vulnerability that allows attackers to cause incorrect Bitcoin addresses to be displa… 2026-05-20 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 medium5.3 CVE-2026-39691 Missing Authorization vulnerability in AdAstraCrypto Cryptocurrency Donation Box – Bitcoin & Crypto Donations cryptocurrency-donation-box allows Exploiting Inc… 2026-04-08 high7.5 CVE-2025-46597 Bitcoin Core 0.13.0 through 29.x has an integer overflow. bitcoin · bitcoin_core 2026-03-20 medium5.3 CVE-2025-46598 Bitcoin Core through 29.0 allows a denial of service via a crafted transaction. bitcoin · bitcoin_core 2026-03-20 low2.0 GHSA-q66h-m87m-j2q6 Bitcoinrb Vulnerable to Command injection via RPC rubygems · bitcoinrb 2026-02-10 medium4.3 CVE-2026-1380 The Bitcoin Donate Button plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. 2026-01-28 critical GHSA-2869-rqcg-vfpc Malware in bitcoin-main-libMalware npm · bitcoin-main-lib 2025-11-27 critical GHSA-6wg2-qx3c-5w54 Malware in bitcoin-lib-jsMalware npm · bitcoin-lib-js 2025-11-27 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 medium5.9 CVE-2025-48102 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in gourl GoUrl Bitcoin Payment Gateway & Paid Downloads & Me… 2025-09-05 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 critical9.3 CVE-2025-26535 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in CodeSolz Bitcoin / AltCoin Payment Gateway for WooCommerc… 2025-03-03 medium5.4 CVE-2025-27579 In Bitaxe ESP-Miner before 2.5.0 with AxeOS, one can use an /api/system CSRF attack to update the payout address (aka stratumUser) for a Bitaxe Bitcoin miner, … Bitaxe ESP-Miner 2025-03-03 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 medium6.1 CVE-2024-12100 The Bitcoin Lightning Publisher for WordPress plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg without appr… 2024-12-24 critical GHSA-29fm-2c66-79qp Malware in bitcoinjs-lib-v6Malware npm · bitcoinjs-lib-v6 2024-12-19 medium5.3 CVE-2024-55563 Bitcoin Core through 27.2 allows transaction-relay jamming via an off-chain protocol attack, a related issue to CVE-2024-52913. bitcoin · bitcoin_core 2024-12-09 medium6.5 CVE-2024-51826 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Jandal Bitcoin Payments bitcoin-payments allows DOM-Based… Bitcoin Payments: from n/a through 2024-11-19 medium6.5 CVE-2024-52922 In Bitcoin Core before 25.1, an attacker can cause a node to not download the latest block, because there can be minutes of delay when an announcing peer stall… bitcoin · bitcoin_core 2024-11-18 medium5.3 CVE-2024-52921 In Bitcoin Core before 25.0, a peer can affect the download state of other peers by sending a mutated block. bitcoin · bitcoin_core 2024-11-18 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 medium6.5 CVE-2024-52919 Bitcoin Core before 22.0 has a CAddrMan nIdCount integer overflow and resultant assertion failure (and daemon exit) via a flood of addr messages. bitcoin · bitcoin_core 2024-11-18 medium6.5 CVE-2024-52918 Bitcoin-Qt in Bitcoin Core before 0.20.0 allows remote attackers to cause a denial of service (memory consumption and application crash) via a BIP21 r paramete… Bitcoin Core 2024-11-18

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.