Comparison Overview
Tigo Paraguay
Tigo Paraguay
Avenida República Argentina , Asunción, 1892, PY
Last Update: 13/12/2025
TU CONEXIÓN A LA VIDA DIGITAL Tigo Paraguay es el proveedor líder en servicios móviles, buscando ser un motor de inclusión digital y transformador de realidades. El servicio móvil cuenta con una gran cobertura, abarcando el 96% del territorio nacional y ofreciendo ade...
AT&T
208 S. Akard Street, Dallas, 75202, US
Last Update: 10/09/2026
We understand that our customers want an easier, less complicated life. We’re using our network, labs, products, services, and people to create a world where everything works together seamlessly, and life is better as a result. How will we continue to drive for thi...
Compliance Ranges Comparison
Tigo Paraguay
AT&T
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Tigo Paraguay in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
AT&T has 967.96% more incidents than the average of all companies with at least one recorded incident.
Incident History - Tigo Paraguay (X = Date, Y = Severity)
Tigo Paraguay cyber incidents detection timeline including parent company and subsidiaries.
Incident History - AT&T (X = Date, Y = Severity)
AT&T cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Tigo Paraguay
AT&T
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.