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
CVE-2026-55250: CWE-294: Authentication Bypass by Capture-replay in macropay-solutions maravel-frameworkCVE-2026-55250 0 CVE-2026-55250 is a high-severity token replay vulnerability in macropay-solutions maravel-framework versions prior to 10.74.0. The issue arises from a lifecycle mismatch between stateless token validation and a caching layer that truncates token blacklist lifespans from 14 days to 2 hours. This allows blacklisted tokens to be accepted after cache eviction or flush, enabling token replay attacks. The vulnerability is due to architectural assumptions in the tymon/jwt-auth package used for API token authentication. Maravel 10.74.0 introduced a partial fix by backporting a new tagged cache implementation, but no direct patch fully resolves the issue without configuration changes. Users must apply a workaround to decouple token identifiers from the tagging cache to preserve the full blacklist lifespan. Join the discussion | CVE Database V5 | 09/08/2026, 22:17:35 UTC Added: 09/08/2026, 22:22:53 UTC |
CVE-2026-53933: CWE-203: Observable Discrepancy in macropay-solutions maravel-frameworkCVE-2026-53933 0 Maravel framework versions prior to 10.73.1 have a side-channel information disclosure vulnerability. The issue occurs when routes with dynamic placeholders are compiled, causing literal placeholder keys to be registered incorrectly. This leads to a 500 Internal Server Error when an attacker sends requests with literal template syntax, revealing internal route parameter names via error responses. Version 10.73.1 includes a patch for this issue. A recommended workaround is to implement middleware that rejects requests containing literal brace patterns before routing. Join the discussion | CVE Database V5 | 09/08/2026, 22:00:17 UTC Added: 09/08/2026, 22:09:30 UTC |
Showing 1 to 2 of 2 results