Comparison Overview
The Max Group
The Max Group
Max House 1,, New Delhi, 110020, IN
Last Update: 08/09/2026
Max Group is a $7 billion diversified Indian conglomerate founded by Mr. Analjit Singh with a strong presence across Senior Care, Life Insurance, and Real Estate. Guided by a purpose-driven approach, we aim to create meaningful solutions that improve lives and deliver l...
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
The Max Group
Angel One
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for The Max Group in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Angel One in 2026.
Incident History - The Max Group (X = Date, Y = Severity)
The Max Group 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
The Max Group
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.