Comparison Overview
BBVA Allianz Seguros
BBVA Allianz Seguros
Calle de Ramírez de Arellano, 35, Madrid, 28043, ES
Last Update: 04/03/2026
Apoyándose en los pilares de la centralidad en el cliente, la excelencia en el servicio, la alta digitalización y el análisis de datos avanzado, BBVA Allianz Seguros es una joint venture nacida para convertirse en el líder mundial en bancaseguros. Dos de los líderes mu...
Marsh Risk
1166 Avenue of the Americas, New York, New York, US, 10036
Last Update: 08/09/2026
We help our clients and colleagues grow — and our communities thrive — by protecting and promoting possibility. We seek better ways to manage risk and define more effective paths to the right outcome. We go beyond risk to rewards for our clients, our company, our collea...
Compliance Ranges Comparison
BBVA Allianz Seguros
Marsh Risk
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for BBVA Allianz Seguros in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Marsh Risk in 2026.
Incident History - BBVA Allianz Seguros (X = Date, Y = Severity)
BBVA Allianz Seguros cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Marsh Risk (X = Date, Y = Severity)
Marsh Risk cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
BBVA Allianz Seguros
Marsh Risk
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.