Comparison Overview
IFC Financial Institutions
IFC Financial Institutions
2121 Pennsylvania Avenue NW, Washington, 20043, US
Last Update: 07/03/2026
In the developing world, 1.7 billion adults do not have a bank account and 200 million businesses lack access to credit. By leveraging our partnerships with financial institutions worldwide, IFC helps to foster financial inclusion, develop resilient financial markets, m...
Sicredi
Av. Assis Brasil, Porto Alegre, 91010-003, BR
Last Update: 17/09/2026
We are born collaborative We believe that change is only possible when everyone works together for the same purpose, after all, cooperativism is in our DNA. Besides this, we know that as important as it is to provide affordable financial solutions it is just as importa...
Compliance Ranges Comparison
IFC Financial Institutions
Sicredi
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for IFC Financial Institutions in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Sicredi in 2026.
Incident History - IFC Financial Institutions (X = Date, Y = Severity)
IFC Financial Institutions cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sicredi (X = Date, Y = Severity)
Sicredi cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
IFC Financial Institutions
Sicredi
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.