Comparison Overview
Tigo Bolivia
Tigo Bolivia
Av Doble Via La Guardia 5to Anillo , Santa Cruz, 00000, BO
Last Update: 20/12/2025
Telefónica Celular de Bolivia S.A. (Telecel S.A.) es una filial del grupo empresarial Millicom, proveedor líder de servicios de cable y móviles dedicado a mercados emergentes en América Latina. Nuestra misión es construir autopistas digitales, que conectan personas, mej...
Idea Cellular Ltd
5th Floor, WINDSOR, Off CST Road, Mumbai, IN
Last Update: 14/09/2026
Idea Cellular is an Aditya Birla Group Company, India's first truly multinational corporation. Idea is a pan-India integrated GSM operator offering 2G and 3G services, and has its own NLD and ILD operations, and ISP license. With revenue in excess of $4 billion; revenue...
Compliance Ranges Comparison
Tigo Bolivia
Idea Cellular Ltd
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Tigo Bolivia in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Idea Cellular Ltd in 2026.
Incident History - Tigo Bolivia (X = Date, Y = Severity)
Tigo Bolivia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Idea Cellular Ltd (X = Date, Y = Severity)
Idea Cellular Ltd cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Tigo Bolivia
Idea Cellular Ltd
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.