Comparison Overview
Webex
Webex
170 West Tasman Drive, San Jose, 95134, US
Last Update: 17/07/2026
Webex is a leading provider of cloud-based collaboration solutions which includes video meetings, calling, messaging, events, customer experience solutions like contact center and purpose-built collaboration devices. At Webex, we start with people and their experience...
Telkom Indonesia
Jalan Jenderal Gatot Subroto Kav. 52, Jakarta Selatan, 40264, ID
Last Update: 13/09/2026
PT Telkom Indonesia (Persero) Tbk (Telkom) is a state-owned information and communications technology enterprise and telecommunications network in Indonesia. The Government of Indonesia is the majority shareholder with 52.09 percent shares while the remaining 47.91 perc...
Compliance Ranges Comparison
Webex
Telkom Indonesia
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
Webex has 5.82% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Telkom Indonesia in 2026.
Incident History - Webex (X = Date, Y = Severity)
Webex cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Telkom Indonesia (X = Date, Y = Severity)
Telkom Indonesia cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Webex
Telkom Indonesia
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.