Comparison Overview
Ascentium Capital
Ascentium Capital
23970 Highway 59 North, Kingwood, 77339, US
Last Update: 03/04/2026
Ascentium Capital, a division of Regions Bank, delivers innovative financing, leasing and working capital solutions through a unique finance platform. This, combined with an exceptional service offering, makes access to capital fast and flexible. Our finance programs be...
Discovery Limited
1 Discovery Place, Sandhurst, Johannesburg, Gauteng, ZA, 2196
Last Update: 01/04/2026
Imagine a world where people live healthier, more enhanced and protected lives… A world in which each organisation is a powerful influencer and responsible corporate citizen, committed to being a force for social good. As a leading innovator in healthcare, wellness, ins...
Compliance Ranges Comparison
Ascentium Capital
Discovery Limited
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Ascentium Capital in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Discovery Limited in 2026.
Incident History - Ascentium Capital (X = Date, Y = Severity)
Ascentium Capital cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Discovery Limited (X = Date, Y = Severity)
Discovery Limited cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Ascentium Capital
Discovery Limited
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.