Comparison Overview
MetroPCS
MetroPCS
12920 SE 38th St, Bellevue, Washington, undefined, US
Last Update: 01/04/2026
Metro by T-Mobile is rethinking wireless with its new mission to give value-conscious consumers a trade-off free wireless experience including all-unlimited plans featuring Amazon Prime and Google One, making it the first and only wireless brand to include Google’s clou...
Reliance Communications
A Block, 2nd Floor, Reliance Communications Limited, DAKC, Kopar Khairane, Navi Mumbai, 400710, IN
Last Update: 08/09/2026
Reliance Communications Limited, founded by the late Shri Dhirubhai H Ambani (1932-2002), has Corporate clientele that includes 40,000 Indian and multinational corporations, including small and medium enterprises. Reliance Communications has established a pan-India, Ne...
Compliance Ranges Comparison
MetroPCS
Reliance Communications
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for MetroPCS in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Reliance Communications in 2026.
Incident History - MetroPCS (X = Date, Y = Severity)
MetroPCS cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Reliance Communications (X = Date, Y = Severity)
Reliance Communications cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
MetroPCS
Reliance Communications
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.