Comparison Overview
Mercer
Mercer
New York, New York, New York, 10036, US
Last Update: 05/09/2026
At Mercer, A Marsh business, we’re helping our clients realize their investment objectives, shape the future of work, and enhance health and retirement outcomes for their people. As a business of Marsh, for 80 years, we’ve been helping our clients, colleagues and comm...
WSP
1600, boul. René-Lévesque ouest, 11e étage, Montreal, Quebec, CA, H3H 1P9
Last Update: 05/09/2026
We are one of the world’s leading professional services firms, uniting our engineering, advisory and science-based expertise to shape communities to advance humanity. From local beginnings to a globe-spanning presence today, we operate in over 50 countries and emplo...
Compliance Ranges Comparison
Mercer
WSP
Benchmark & Cyber Underwriting Signals
Incidents vs Professional Services Industry Avg (This Year)
No incidents recorded for Mercer in 2026.
Incidents vs Professional Services Industry Avg (This Year)
No incidents recorded for WSP in 2026.
Incident History - Mercer (X = Date, Y = Severity)
Mercer cyber incidents detection timeline including parent company and subsidiaries.
Incident History - WSP (X = Date, Y = Severity)
WSP cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Mercer
WSP
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.