Comparison Overview
SEB Eesti
SEB Eesti
Tornimäe 2, Tallinn, 15010, EE
Last Update: 07/01/2026
SEB on pikaajalistel kliendisuhetel põhinev kaasaegne universaalpank. Meie eesmärgiks on aidata inimestel ja ettevõtetel saavutada edu, pakkudes neile finantsvahendeid ja head nõu. Tahame olla parimate kliendisuhetega usaldusväärseim pank Eestis. SEB Grupp tervikuna on...
IFC - International Finance Corporation
2121 Pennsylvania Ave NW, Washington, 20433, US
Last Update: 08/09/2026
IFC, a member of the World Bank Group, is the largest global development institution focused exclusively on the private sector in developing countries. We utilize and leverage our products and services—as well as products and services of other institutions in the World...
Compliance Ranges Comparison
SEB Eesti
IFC - International Finance Corporation
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for SEB Eesti in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for IFC - International Finance Corporation in 2026.
Incident History - SEB Eesti (X = Date, Y = Severity)
SEB Eesti cyber incidents detection timeline including parent company and subsidiaries.
Incident History - IFC - International Finance Corporation (X = Date, Y = Severity)
IFC - International Finance Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
SEB Eesti
IFC - International Finance Corporation
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.