Comparison Overview
Banco Pichincha
Banco Pichincha
Amazonas 4560 y Pereira, Quito, EC
Last Update: 29/03/2026
En Banco Pichincha estamos conscientes que hay nuevas maneras de ver el mundo; por eso, queremos aprovechar nuestra posición de liderazgo en Ecuador, avalada por 119 años de historia, para acercar a nuestros clientes las oportunidades que brinda la nueva era en que vivi...
ING Nederland
Amsterdam Zuidoost, 1102 CT Netherlands, Amsterdam Zuidoost, 1102 CT, NL
Last Update: 29/03/2026
ING ING is a global bank with a strong European base. With 14,500 employees in the Netherlands, we’re one of the biggest employers of the country. Our research tells us that we stand out here because of our great working culture, competitive benefits, and interesting wo...
Compliance Ranges Comparison
Banco Pichincha
ING Nederland
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Banco Pichincha in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for ING Nederland in 2026.
Incident History - Banco Pichincha (X = Date, Y = Severity)
Banco Pichincha cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ING Nederland (X = Date, Y = Severity)
ING Nederland cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Banco Pichincha
ING Nederland
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.