Comparison Overview
Colliers Securities
Colliers Securities
90 S 7th St, Minneapolis, Minnesota, 55402, US
Last Update: 01/11/2025
Colliers Securities (part of Colliers | U.S.) is a full-service investment bank and registered securities broker-dealer committed to providing a full spectrum of products and services tailored to meet the needs of individual and institutional investors nationwide. We h...
SMBC Group
1丁目 1-2, Marunouchi Chiyoda-Ku,, Tokyo, JP
Last Update: 14/09/2026
SMBC Group is a leading global financial group with a 400-year history and a network spanning nearly 40 countries and regions. We partner with clients around the world, providing a broad range of financial services—from Corporate & Investment Banking and Global Markets...
Compliance Ranges Comparison
Colliers Securities
SMBC Group
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Colliers Securities in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for SMBC Group in 2026.
Incident History - Colliers Securities (X = Date, Y = Severity)
Colliers Securities cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SMBC Group (X = Date, Y = Severity)
SMBC Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Colliers Securities
SMBC Group
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.