Comparison Overview
Sparkasse Pforzheim Calw
Sparkasse Pforzheim Calw
Poststraße 3, Pforzheim, 75172, DE
Last Update: 08/03/2026
Sparkasse Pforzheim Calw: Mit Herz und Hand - seit über 175 Jahren die führende Bank in Pforzheim, Calw und Enzkreis. Impressum: http://www.sparkasse-pfcw.de/impressum
BDO Unibank
7899 Makati Ave, Makati, 0726, PH
Last Update: 09/09/2026
BDO is a full-service universal bank in the Philippines. It provides a complete array of industry-leading products and services including Lending (corporate and consumer), Deposit-taking, Foreign Exchange, Brokering, Trust and Investments, Credit Cards, Corporate Cash M...
Compliance Ranges Comparison
Sparkasse Pforzheim Calw
BDO Unibank
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Sparkasse Pforzheim Calw in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for BDO Unibank in 2026.
Incident History - Sparkasse Pforzheim Calw (X = Date, Y = Severity)
Sparkasse Pforzheim Calw cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BDO Unibank (X = Date, Y = Severity)
BDO Unibank cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Sparkasse Pforzheim Calw
BDO Unibank
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.