Comparison Overview
Munich Re
Munich Re
Königinstrasse 107, Munich, 80802, DE
Last Update: 04/09/2026
Munich Re is one of the world’s leading providers of reinsurance, primary insurance and insurance-related risk solutions. The group consists of the reinsurance and ERGO business segments, as well as the capital investment company MEAG. We are globally active and operate...
Travelers
485 Lexington Avenue, New York, NY, US, 10017-2630
Last Update: 18/09/2026
Travelers provides insurance coverage to protect the things that are important to you – your home, your car, your valuables and your business. We have been around for more than 170 years and have earned a reputation as one of the best property casualty insurers in the i...
Compliance Ranges Comparison
Munich Re
Travelers
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
Munich Re has 34.64% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Travelers in 2026.
Incident History - Munich Re (X = Date, Y = Severity)
Munich Re cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Travelers (X = Date, Y = Severity)
Travelers cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Munich Re
Travelers
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.