Comparison Overview
Hackerdogs
Hackerdogs
N/A
Last Update: 11/04/2026
Our Mission "To deliver the right intelligence, at the right time, to the right people." What we do We have built an AI-native Autonomous Threat Exposure Management (ATEM) platform that delivers evidence-backed, actionable intelligence to help protect your global asset...
Prosegur
Pajaritos, 24, Madrid, 28007, ES
Last Update: 02/04/2026
At Prosegur, being aware of who we are is what defines our identity and commitment. 🌐 We are Prosegur. Leaders in the private security sector for more than 45 years and in more than 30 countries. 💡 We are innovation. We reinvent ourselves, adapt and integrate trends t...
Compliance Ranges Comparison
Hackerdogs
Prosegur
Benchmark & Cyber Underwriting Signals
Incidents vs Security and Investigations Industry Avg (This Year)
No incidents recorded for Hackerdogs in 2026.
Incidents vs Security and Investigations Industry Avg (This Year)
No incidents recorded for Prosegur in 2026.
Incident History - Hackerdogs (X = Date, Y = Severity)
Hackerdogs cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Prosegur (X = Date, Y = Severity)
Prosegur cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Hackerdogs
Prosegur
FAQ
Latest Global CVEs
vLLM through 0.29.0 fails to properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/push_worker.py#L162-L181
- https://github.com/vllm-project/vllm/pull/55677
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-rejected-requests
redis-parser through 3.0.0 contains a denial of service vulnerability in the RESP protocol parser that allows malicious Redis endpoints to crash the client process through unbounded recursion on nested arrays. Attackers can send crafted RESP byte streams with repeated array headers that exhaust the V8 call stack, causing an uncaught RangeError that terminates the Node.js process without triggering error handling callbacks.
- https://github.com/NodeRedis/node-redis-parser
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L204-L213
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L291-L306
- https://github.com/redis/ioredis/issues/2108
- https://www.vulncheck.com/advisories/redis-parser-through-3.0.0-denial-of-service-via-unbounded-recursion
Improper neutralization of special elements in output used by a downstream component ('injection') in Azure Cosmos DB allows an authorized attacker to elevate privileges over a network.
Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.