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 CVE-2026-67531 is a critical remote code execution vulnerability in the agentfront frontmcp framework prior to version 1.5.7. It arises from improper control of code generation due to exposure of live host Zod schema instances in sandboxed scripts. This allows an attacker to escape the sandbox and execute arbitrary code with the server user's privileges, potentially exposing sensitive secrets and credentials. The vulnerability is fixed in version 1.5.7. Join the discussion | CVE Database V5 | 08/05/2026, 22:54:36 UTC Added: 08/05/2026, 23:26:44 UTC |
CVE-2026-39885 is a Server-Side Request Forgery (SSRF) vulnerability in the frontmcp product by agentfront, specifically in versions prior to 1.0.4. The vulnerability arises because the mcp-from-openapi library uses @apidevtools/json-schema-ref-parser to dereference $ref pointers in OpenAPI specifications without restricting URLs or using custom resolvers. This allows malicious OpenAPI specs to cause the server to fetch internal network resources, cloud metadata endpoints, or local files during initialization, enabling SSRF and local file read attacks. The vulnerability has a high severity with a CVSS score of 7.5. No official patch or remediation level is explicitly stated in the provided data, but the description notes the issue is fixed in version 2.3.0 of the framework, which suggests upgrading to a fixed version is the recommended mitigation. Join the discussion | CVE Database V5 | 04/08/2026, 20:34:20 UTC Added: 04/08/2026, 20:50:48 UTC |
Showing 1 to 2 of 2 results