Comparison Overview
Oliver Wyman Actuarial
Oliver Wyman Actuarial
1166 Avenue of Americas, New York, 10036, US
Last Update: 01/03/2026
We guide clients through high-stakes decisions and transformative moments so they can adapt, grow, and thrive. Our edge? The power of perspective — driven by deep industry insight, specialized expertise, and a spirit of true collaboration.
Primerica
1 Primerica Parkway, Duluth, 30099-0001, US
Last Update: 17/09/2026
Primerica is a leading provider of financial products and services in North America, with over 2,800 corporate employees who support over 151,000 licensed independent representatives providing financial education and offering financial products and services to their cli...
Compliance Ranges Comparison
Oliver Wyman Actuarial
Primerica
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Oliver Wyman Actuarial in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Primerica in 2026.
Incident History - Oliver Wyman Actuarial (X = Date, Y = Severity)
Oliver Wyman Actuarial cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Primerica (X = Date, Y = Severity)
Primerica cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Oliver Wyman Actuarial
Primerica
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.