Threat Intelligence Database
Comprehensive database of the latest cyber threats affecting organizations worldwide. Filter and search to find specific threat intelligence relevant to your organization.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threat Intelligence
Click on any threat for detailed analysis and mitigation recommendations
A reachable assertion vulnerability exists in Nimiq's network-libp2p prior to version 1.3.0. The network-libp2p discovery protocol handler incorrectly assumes only one inbound and one outbound discovery substream per connection. If a remote peer opens a second discovery substream on the same connection, the handler triggers a panic, causing the networking task to crash and the node's p2p networking to go offline until restarted. This denial-of-service condition affects availability but does not impact confidentiality or integrity. The issue is fixed in version 1.3.0. No known workarounds are available. Join the discussion | CVE Database V5 | 04/22/2026, 19:40:26 UTC Added: 04/22/2026, 20:01:07 UTC |
0 CVE-2026-34062 is a medium severity vulnerability in the nimiq network-libp2p prior to version 1.3.0. It involves allocation of resources without limits or throttling, where inbound substreams can be kept open indefinitely by a remote peer sending only partial frames. This leads to a larger stalled-slot budget than intended, potentially causing denial of service by exhausting resources. The issue is addressed in version 1.3.0, which includes a formal patch. No known workarounds exist. Join the discussion | CVE Database V5 | 04/22/2026, 19:23:36 UTC Added: 04/22/2026, 20:01:07 UTC |
Showing 1 to 2 of 2 results