Comparison Overview
Alera Group (TRUEbenefits)
Alera Group (TRUEbenefits)
601 Union Street, Seattle, 98101, US
Last Update: 30/03/2026
Beyond Benefits as Usual We ask questions you haven’t heard before. Digging deeper gives us the understanding to customize cost-effective solutions that advance our clients’ business goals, see them through times of rapid change, and help recruit and retain the best pe...
Aviva
80 Fenchurch Street, London, EC3M 4AE, , GB
Last Update: 04/09/2026
💛 We're a leading Insurance, Wealth & Retirement business. 📣 Follow for #LifeAtAviva. Aviva is nothing without our people. Living up to our purpose to be with you today for a better tomorrow applies to those we work with just as much as it does to our custom...
Compliance Ranges Comparison
Alera Group (TRUEbenefits)
Aviva
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Alera Group (TRUEbenefits) in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Aviva in 2026.
Incident History - Alera Group (TRUEbenefits) (X = Date, Y = Severity)
Alera Group (TRUEbenefits) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Aviva (X = Date, Y = Severity)
Aviva cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Alera Group (TRUEbenefits)
Aviva
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.