Comparison Overview
Grupo DKV
Grupo DKV
Avd. María Zambrano, 31, None, Zaragoza, Zaragoza, ES, 50018
Last Update: 04/03/2026
Grupo DKV pertenece a Munich Health, la división que agrupa las compañías especialistas en salud de Munich Re desde 2006. El grupo asegurador Munich Re, en el ámbito de la salud, combina su conocimiento global en seguros y reaseguros, incluidos los servicios. En Espa...
Brown & Brown
300 N Beach St, Daytona Beach, 32114, US
Last Update: 05/09/2026
Brown & Brown delivers risk management solutions to help protect and preserve what our customers value most. Our two business segments, Retail and Specialty Distribution, offer businesses and individuals a wide range of insurance solutions. We are one of the insurance ...
Compliance Ranges Comparison
Grupo DKV
Brown & Brown
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Grupo DKV in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Brown & Brown in 2026.
Incident History - Grupo DKV (X = Date, Y = Severity)
Grupo DKV cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Brown & Brown (X = Date, Y = Severity)
Brown & Brown cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Grupo DKV
Brown & Brown
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.