Comparison Overview
Jarislowsky, Fraser Limited
Jarislowsky, Fraser Limited
1010 Rue Sherbrooke O, Montreal, Quebec, H3A 2R7, CA
Last Update: 14/02/2026
Jarislowsky, Fraser Limitée est l'une des principales firme de gestion de placements au Canada. Fondée en 1955 comme une boutique de recherche, Jarislowsky Fraser gère aujourd'hui les portefeuilles de fonds de pension, de fondations et de dotation, de peuples autochtone...
Old Mutual
107 Rivonia Rd, Johannesburg, ZA
Last Update: 18/09/2026
Old Mutual Limited is a listed company on the Johannesburg Stock Exchange and has secondary listings on the London, Malawi, Namibia and Zimbabwe stock exchanges. As a Pan-African financial services company, we are focused on Africa, her needs and her people. Together w...
Compliance Ranges Comparison
Jarislowsky, Fraser Limited
Old Mutual
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Jarislowsky, Fraser Limited in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Old Mutual in 2026.
Incident History - Jarislowsky, Fraser Limited (X = Date, Y = Severity)
Jarislowsky, Fraser Limited cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Old Mutual (X = Date, Y = Severity)
Old Mutual cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Jarislowsky, Fraser Limited
Old Mutual
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.