Comparison Overview
Bell Business
Bell Business
Carref Alexandre-Graham-Bell, Montreal, Quebec, CA, H3E
Last Update: 08/03/2026
Now more than ever, organizations need to connect a sophisticated set of communication platforms, solutions and tools to deliver the best experiences for their customers and employees. How we support them has been shaped by these challenges: Empowering the Connected Ent...
Vodafone Idea Limited
Vodafone Idea Limited, Mumbai, 400030, IN
Last Update: 05/09/2026
Vodafone Idea Limited is an Aditya Birla Group and Vodafone Group partnership. It is India’s leading telecom service provider. The Company provides pan India Voice and Data services across 2G, 3G and 4G platform. With the large spectrum portfolio to support the growing ...
Compliance Ranges Comparison
Bell Business
Vodafone Idea Limited
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Bell Business in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Vodafone Idea Limited in 2026.
Incident History - Bell Business (X = Date, Y = Severity)
Bell Business cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Vodafone Idea Limited (X = Date, Y = Severity)
Vodafone Idea Limited cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Bell Business
Vodafone Idea Limited
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.