Comparison Overview
Ooredoo Algerie

Ooredoo Algerie
66, Route de Ouled Fayet, Chéraga, 16001, DZ
Last Update: 31/03/2026
A leading international communications company, with a significant presence in the MENA region. Principle activities are mobile telephone services, broadband solutions, digital futures and fiber technologies, serving both consumer and business markets

Spectrum
Stamford , 06901, US
Last Update: 05/09/2026
Spectrum is a suite of advanced communications services offered by Charter Communications, Inc. (NASDAQ:CHTR), a leading broadband connectivity company available to more than 57 million homes and small to large businesses across 41 states. Founded in 1993, Charter has e...
Compliance Ranges Comparison

Ooredoo Algerie







Spectrum






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Ooredoo Algerie in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
Spectrum has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Ooredoo Algerie (X = Date, Y = Severity)
Ooredoo Algerie cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Spectrum (X = Date, Y = Severity)
Spectrum cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Ooredoo Algerie

Spectrum
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.