Comparison Overview
Tigo Guatemala
Tigo Guatemala
Km 9.5 Ctra a El Salvador, Santa Catarina Pinula, Guatemala 01051, Carr. a El Salvador Ctra a El Salvador km 9.5, Guatemala 01051, Guatemala, Guatemala, 01051, GT
Last Update: 28/01/2026
Nuestra Visión, permitir a todos avanzar y disfrutar de la vida. Lema que nace de un sueño de contribuir en el desarrollo de Guatemala, permitir a cada persona que tiene contacto con Tigo, el acceso a su mundo. Nuestro mayor diferenciador, tener la mejor señal y c...
BT Group
One Braham, London, E1 8EE, GB
Last Update: 13/09/2026
We’re one of the world’s leading communications services companies. At BT Group, the solutions we sell are integral to modern life. Our purpose is as simple as it is ambitious: we connect for good. There are no limits to what people can do when they connect. And as te...
Compliance Ranges Comparison
Tigo Guatemala
BT Group
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Tigo Guatemala in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for BT Group in 2026.
Incident History - Tigo Guatemala (X = Date, Y = Severity)
Tigo Guatemala cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BT Group (X = Date, Y = Severity)
BT Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Tigo Guatemala
BT 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.