Comparison Overview
D.A. Davidson Companies
D.A. Davidson Companies
8 3rd St N, Great Falls, 59401, US
Last Update: 31/03/2026
At D.A. Davidson Companies, we identify and evaluate market trends, investment ideas and business opportunities, and turn them into actionable insights and strategies. Founded in 1935 as a small brokerage firm, D.A. Davidson has grown into a diversified financial servic...
Pru Life UK
9F Uptown Place Tower 1, 1 East 11th Drive, Uptown Bonifacio, Taguig City, 1634, PH
Last Update: 02/04/2026
With 29 years of operations in the Philippines, we have the largest agency force of more than 39,000 licensed financial advisers ready to listen, understand and deliver. We are an innovative force in the life insurance industry who pioneered investment-linked or unit-li...
Compliance Ranges Comparison
D.A. Davidson Companies
Pru Life UK
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for D.A. Davidson Companies in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Pru Life UK in 2026.
Incident History - D.A. Davidson Companies (X = Date, Y = Severity)
D.A. Davidson Companies cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Pru Life UK (X = Date, Y = Severity)
Pru Life UK cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
D.A. Davidson Companies
Pru Life UK
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.