Comparison Overview
HSBC
HSBC
8 Canada Square, London, E14 5HQ, GB
Last Update: 05/09/2026
Opening up a world of opportunity for our customers, investors, ourselves and the planet. We're a financial services organisation that serves more than 40 million customers, ranging from individual savers and investors to some of the world’s biggest companies and gover...
Angel One
G-1, Ackruti Trade Center, Road No -7, MIDC, Andheri (E), Mumbai, Maharashtra, IN, 400 093
Last Update: 06/09/2026
Angel One Limited is a Fintech company providing broking services, margin trading facility, research services, depository services, investment education and distribution of third-party financial products to its clients, on a mission to become the No. 1 fintech organizat...
Compliance Ranges Comparison
HSBC
Angel One
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for HSBC in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Angel One in 2026.
Incident History - HSBC (X = Date, Y = Severity)
HSBC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Angel One (X = Date, Y = Severity)
Angel One cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
HSBC
Angel One
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.