Comparison Overview
ING Italia

ING Italia
Viale Fulvio Testi, 250, Milan, Lombardy, undefined, IT
Last Update: 21/12/2025
ING ti incoraggia a vivere pienamente ogni occasione, dalla più semplice alla più grande, nella vita privata come in quella professionale. In una parola, anzi tre: do your thing! Con ING puoi dedicarti a ciò che conta davvero per te, mentre alla banca pensiamo noi, co...

BNP Paribas
16 boulevard des Italiens, Paris, FR, 75009
Last Update: 12/09/2026
BNP Paribas is a leading bank in Europe with an international reach. It has a presence in 64 countries, with more than 178,000 employees, including more than 144,000 in Europe. BNP Paribas holds leading positions in its three major operating divisions: ⚆ Commercial, P...
Compliance Ranges Comparison

ING Italia







BNP Paribas






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

ING Italia

BNP Paribas
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.