Comparison Overview
Westpac
Westpac
Head Office: 200 Barangaroo Avenue, Sydney, 2000, AU
Last Update: 14/09/2026
To turn doing into done, it takes a little Westpac. From rescue helicopters and signing the Equator Principles, to paying super during parental leave and initiatives like Westpac SaferPay and SafeCall that help protect customers from scams... we have a proud history of...
IDBI Bank
IDBI Tower, WTC Complex,, Mumbai, 400005, IN
Last Update: 02/04/2026
Welcome to IDBI Bank's LinkedIn page! We are a leading bank in India, with a rich legacy. At IDBI Bank, we believe in empowering our customers by providing them with a wide range of banking products and services to meet their financial needs. Whether you are an indivi...
Compliance Ranges Comparison
Westpac
IDBI Bank
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Westpac in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for IDBI Bank in 2026.
Incident History - Westpac (X = Date, Y = Severity)
Westpac cyber incidents detection timeline including parent company and subsidiaries.
Incident History - IDBI Bank (X = Date, Y = Severity)
IDBI Bank cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Westpac
IDBI Bank
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.