Comparison Overview
Nordea
Nordea
Aleksanterinkatu 36 B, Helsinki, FI
Last Update: 14/09/2026
We are a universal bank with a 200-year history of supporting and growing the Nordic economies – enabling dreams and aspirations for a greater good. Every day, we work to support our customers’ financial development, delivering best-in-class omnichannel customer experie...
Societe Generale
29, boulevard Haussmann, Paris, 75009, FR
Last Update: 17/09/2026
Societe Generale is one of the leading European financial services groups. Based on a diversified and integrated banking model, the Group combines financial strength and proven expertise in innovation with a strategy of sustainable growth. Committed to the positive tran...
Compliance Ranges Comparison
Nordea
Societe Generale
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Nordea in 2026.
Incidents vs Banking Industry Avg (This Year)
Societe Generale has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Nordea (X = Date, Y = Severity)
Nordea cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Societe Generale (X = Date, Y = Severity)
Societe Generale cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Nordea
Societe Generale
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.