Comparison Overview
NAB
NAB
700 Bourke St, Melbourne, 3008, AU
Last Update: 27/02/2026
We're here to be the most customer-centric company in Australia and New Zealand. We’re focused on what matters most and here to support you with your banking needs in any way we can. We’re open for business. Connect with us: www.nab.com.au/contact-us
Caisse d’Epargne
50 avenue Pierre Mendes France, Paris, 75012, FR
Last Update: 02/04/2026
Banques coopératives, les Caisses d'Epargne conjuguent depuis 1818 confiance, solidarité et modernité. Deuxième réseau bancaire en France, les 16 Caisses d'Epargne régionales comptent parmi les premières banques de leur région. Elles accompagnent tous les acteurs écon...
Compliance Ranges Comparison
NAB
Caisse d’Epargne
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for NAB in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Caisse d’Epargne in 2026.
Incident History - NAB (X = Date, Y = Severity)
NAB cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Caisse d’Epargne (X = Date, Y = Severity)
Caisse d’Epargne cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
NAB
Caisse d’Epargne
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.