Comparison Overview
ING Luxembourg
ING Luxembourg
26 Place de la Gare, Luxembourg, undefined, L-1616, LU
Last Update: 29/12/2025
At ING, we believe all sustainable progress is driven by people with the imagination and determination to improve their future and the futures of those around them. Our purpose is therefore to empower people to stay a step ahead in life and in business. As a global fina...
Capitec
5 Neutron Road, Stellenbosch, Western Cape, ZA, 7600
Last Update: 02/04/2026
Imagine simple, affordable banking solutions that work for you – just like it does for over 25 million South Africans. They’re banking smart, paying less and getting more value every day with us. As the country’s leading digital bank, we’re proud to have been voted th...
Compliance Ranges Comparison
ING Luxembourg
Capitec
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for ING Luxembourg in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Capitec in 2026.
Incident History - ING Luxembourg (X = Date, Y = Severity)
ING Luxembourg cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Capitec (X = Date, Y = Severity)
Capitec cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
ING Luxembourg
Capitec
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.