Comparison Overview
Westpac Private Bank
Westpac Private Bank
200 Barangaroo Ave, Sydney, 2000, AU
Last Update: 30/04/2026
At Westpac Private Bank, we’ve built relationships of confidence and trust with high net worth individuals and their families over generations. We are committed to providing outstanding personalised service and innovative global investment opportunities to our clients. ...
Banco Sabadell
BANCO SABADELL, Pl. Sant Roc, 20, Sabadell, Barcelona, ES, 08201
Last Update: 03/04/2026
Banco Sabadell es el cuarto grupo bancario privado español, integrado por diferentes bancos, marcas, sociedades filiales y sociedades participadas que abarcan todos los ámbitos del negocio financiero bajo un denominador común: profesionalidad y calidad. Un equipo hum...
Compliance Ranges Comparison
Westpac Private Bank
Banco Sabadell
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Westpac Private Bank in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Banco Sabadell in 2026.
Incident History - Westpac Private Bank (X = Date, Y = Severity)
Westpac Private Bank cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Banco Sabadell (X = Date, Y = Severity)
Banco Sabadell cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Westpac Private Bank
Banco Sabadell
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.