Comparison Overview
ING Intermediair Zakelijk
ING Intermediair Zakelijk
Bijlmerdreef 24, Amsterdam, 1102 CT, NL
Last Update: 12/03/2026
Jij kent de ondernemer en zijn financiële situatie als geen ander. Daarom werken we graag met jou samen. Op deze pagina vind je relevante updates, inspirerende verhalen en inzichten die je helpen je klant nog beter te adviseren. Wil je even sparren over een financierin...
Garanti BBVA
Nisbetiye Mh., Aytar Caddesi No:2 Zincirlikuyu, Istanbul, Istanbul, TR
Last Update: 31/03/2026
With a digitalization and people oriented vision, we contribute to our economy and society. We make great efforts to help you make the best financial decisions by offering you the opportunities of the future with our dynamic business model, pioneering technology and inn...
Compliance Ranges Comparison
ING Intermediair Zakelijk
Garanti BBVA
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for ING Intermediair Zakelijk in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Garanti BBVA in 2026.
Incident History - ING Intermediair Zakelijk (X = Date, Y = Severity)
ING Intermediair Zakelijk cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Garanti BBVA (X = Date, Y = Severity)
Garanti BBVA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
ING Intermediair Zakelijk
Garanti BBVA
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.