Comparison Overview
Slovak Telekom
Slovak Telekom
Bajkalská 28, Bratislava, 817 62, SK
Last Update: 02/04/2026
Slovak Telekom, member of the multinational Deutsche Telekom Group, is the largest Slovak multimedia operator with many years of experience and responsible approach to doing business. Slovak Telekom offers a full range of data and voice services, owns and operates the f...
Optus
1 Lyonpark Road, Macquarie Park, 2113, AU
Last Update: 07/09/2026
Optus is an Australian telecommunications company, delivering more than 11 million services to our customers every day across mobile, broadband and digital solutions. Message our dedicated Social Media Care team at help.optus.com.au/contactus for 24/7 assistance with y...
Compliance Ranges Comparison
Slovak Telekom
Optus
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Slovak Telekom in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
Optus has 191.26% more incidents than the average of all companies with at least one recorded incident.
Incident History - Slovak Telekom (X = Date, Y = Severity)
Slovak Telekom cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Optus (X = Date, Y = Severity)
Optus cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Slovak Telekom
Optus
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.