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 Skipper is an HTTP router and reverse proxy for service composition. Prior to 0.26.10, zalando/skipper's OpenPolicyAgent integration silently bypasses request-body inspection on HTTP/1.1 Transfer-Encoding: chunked and HTTP/2 requests that omit the content-length pseudo-header, because the opaAuthorizeRequestWithBody filter and OpenPolicyAgentInstance.ExtractHttpBodyOptionally in filters/openpolicyagent/openpolicyagent.go produce an empty raw_body and input.parsed_body while the upstream service receives the full attacker-controlled body. This issue is fixed in version 0.26.10. Join the discussion | CVE Database V5 | 07/17/2026, 19:23:43 UTC Added: 07/18/2026, 11:08:32 UTC |
0 CVE-2026-24470 is a high-severity vulnerability in Zalando's Skipper HTTP router and reverse proxy, versions prior to 0.24.0. When used as a Kubernetes Ingress controller, it allows users with permissions to create Ingress and ExternalName Services to route traffic through Skipper to internal services, effectively bypassing network restrictions. This unintended proxy or 'confused deputy' flaw can lead to high confidentiality and integrity impacts without requiring user interaction. The vulnerability is mitigated in version 0.24.0 by disabling ExternalName Services by default and can be further controlled by allow-listing targets. European organizations using Skipper in Kubernetes environments should prioritize upgrading and applying strict allow-listing to prevent unauthorized internal access. Countries with strong Kubernetes adoption and critical cloud-native infrastructure, such as Germany, the UK, and the Netherlands, are most likely to be affected. Join the discussion | CVE Database V5 | 01/26/2026, 22:23:43 UTC Added: 01/26/2026, 22:50:56 UTC |
Showing 1 to 2 of 2 results