Comparison Overview
Degroof Petercam
Degroof Petercam
Rue de l'Industrie 44, Brussels, 1040, BE
Last Update: 28/03/2026
Founded in 1871, Degroof Petercam is a Belgian-rooted reference investment house, built on more than 150 years of integrated financial knowledge. As responsible employer and investor, we contribute to sustainable growth. Private clients and families, entrepreneurs, corp...
SBI Card
Infinity Tower, DLF City Phase 2, Gurgaon, 122002, IN
Last Update: 10/09/2026
SBI Card was launched in 1998 with the State Bank of India, India's largest bank, as the majority stakeholder. In March 2020, SBI Card was listed on BSE and NSE. Today, SBI Card is India’s largest pure-play credit card issuer with over 20 million cards in force, as of D...
Compliance Ranges Comparison
Degroof Petercam
SBI Card
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Degroof Petercam in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for SBI Card in 2026.
Incident History - Degroof Petercam (X = Date, Y = Severity)
Degroof Petercam cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SBI Card (X = Date, Y = Severity)
SBI Card cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Degroof Petercam
SBI Card
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.