Comparison Overview
Bandhan Life

Bandhan Life
Leela Business Park, A - 201, 2nd, Mumbai, 400059, IN
Last Update: 27/02/2026
Welcome to Bandhan Life—where ambitions are empowered, and lives are secured! At Bandhan Life, we simplify life insurance to make it: ✔️ Easy to Understand ✔️ Simple to Buy ✔️ Straightforward to Claim Everything you need to empower your ambitions and secure your dre...

IAG
201 Sussex St, Sydney, 2000, AU
Last Update: 04/09/2026
IAG is Australia and New Zealand's largest general insurance company with a purpose to make your world a safer place, whether you are a customer, partner, employee, shareholder or part of the communities IAG serves across Australia and New Zealand. Our businesses have ...
Compliance Ranges Comparison

Bandhan Life







IAG






Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Bandhan Life in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for IAG in 2026.
Incident History - Bandhan Life (X = Date, Y = Severity)
Bandhan Life cyber incidents detection timeline including parent company and subsidiaries.
Incident History - IAG (X = Date, Y = Severity)
IAG cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Bandhan Life

IAG
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.