Comparison Overview
American Tower Asia
American Tower Asia
Plot No. 14-A, Sector-18, GURUGRAM, HARYANA, 122015, IN
Last Update: 16/03/2026
Through a global portfolio of digital infrastructure assets and other communications real estate solutions, American Tower enables our partners and customers to keep people and communities connected in a responsible, equitable and sustainable way. With the increasing p...
T-Mobile
12920 SE 38th St, Bellevue, 98006, US
Last Update: 15/09/2026
As the supercharged Un-carrier, T-Mobile US, Inc. (NASDAQ: TMUS) is powered by an award-winning 5G network that connects more people, in more places, than ever before. With T-Mobile’s unique value proposition of best network, best value, and best experiences, the Un-car...
Compliance Ranges Comparison
American Tower Asia
T-Mobile
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for American Tower Asia in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
T-Mobile has 288.35% more incidents than the average of all companies with at least one recorded incident.
Incident History - American Tower Asia (X = Date, Y = Severity)
American Tower Asia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - T-Mobile (X = Date, Y = Severity)
T-Mobile cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
American Tower Asia
T-Mobile
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.