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
0 Previously, resolving relative paths containing parent directory ('..') segments performed string conversions and buffer rewrites on each step, resulting in quadratic time complexity and high memory allocation overhead. Now, path resolution operates on a byte buffer using index-based backtracking for '..' segments, eliminating the quadratic time complexity and significantly reducing memory allocations. Join the discussion | CVE Database V5 | 08/13/2026, 21:58:53 UTC Added: 08/13/2026, 22:11:58 UTC |
0 url.Parse insufficiently validated the host/authority component and accepted some invalid URLs. Join the discussion | CVE Database V5 | 03/06/2026, 21:28:14 UTC Added: 03/06/2026, 21:46:07 UTC |
0 The net/url package does not set a limit on the number of query parameters in a query. While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption. Join the discussion | CVE Database V5 | 01/28/2026, 19:30:31 UTC Added: 01/28/2026, 19:36:27 UTC |
0 The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement. Join the discussion | CVE Database V5 | 10/29/2025, 22:10:13 UTC Added: 10/29/2025, 22:24:04 UTC |
Showing 1 to 4 of 4 results