Comparison Overview
congstar
congstar
Bayenwerft 12-14, Köln, 50678, DE
Last Update: 28/03/2026
Fairness, Vielfalt und Du. Wir sind ein buntes Team aus über 280 congstars und gehören zu einem der besten Arbeitgeber sowie führenden Mobilfunkanbietern Deutschlands. Du findest uns mitten im Herzen von Köln im wunderschönen Rheinauhafen oder remote im Homeoffice. ...
Bell
1 carrefour Alexandre-Graham-Bell, Montreal, Quebec, CA, H3E 3B3
Last Update: 05/09/2026
We advance how people connect with each other and the world #ConnectionIsEverything. Bell is Canada's largest communications company providing advanced Bell broadband wireless, Internet, TV, media and business communications services. Founded in Montréal in 1880, Bell...
Compliance Ranges Comparison
congstar
Bell
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for congstar in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
Bell has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - congstar (X = Date, Y = Severity)
congstar cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bell (X = Date, Y = Severity)
Bell cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
congstar
Bell
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.