Comparison Overview
Merrill Lynch
Merrill Lynch
2 World Financial Center, New York, 10281, US
Last Update: 13/09/2026
Founded in 1914, Merrill is one of the largest wealth management businesses in the world. Merrill financial advisors combine financial knowledge and experience with a deep understanding of their clients’ needs to help their clients pursue the lives they want. With a dee...
Lincoln Financial
150 N. Radnor-Chester Road, Radnor, PA, US, 19087
Last Update: 09/09/2026
Lincoln Financial (NYSE: LNC) helps people to confidently plan for their version of a successful future. We focus on identifying a clear path to financial security, with products including annuities, investments, life insurance, group protection, and retirement plan ser...
Compliance Ranges Comparison
Merrill Lynch
Lincoln Financial
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Merrill Lynch in 2026.
Incidents vs Financial Services Industry Avg (This Year)
Lincoln Financial has 94.17% more incidents than the average of all companies with at least one recorded incident.
Incident History - Merrill Lynch (X = Date, Y = Severity)
Merrill Lynch cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lincoln Financial (X = Date, Y = Severity)
Lincoln Financial cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Merrill Lynch
Lincoln Financial
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.