Comparison Overview
Telkomsel Enterprise
Telkomsel Enterprise
Jakarta, ID
Last Update: 11/03/2026
Telkomsel Enterprise memahami bahwa setiap bisnis perlu bertransformasi digital untuk terus tumbuh bahkan menjadi game-changer dalam ekonomi digital saat ini. Jadikan proses bisnismu lebih efisien dan produktif dengan solusi pasti yang sesuai kebutuhan di http://Tsel....
Reply
C.so Francia, 110, Turin, 10143, IT
Last Update: 09/09/2026
Reply [EXM, STAR: REY] specialises in the design and implementation of solutions based on new communication channels and digital media. As a network of highly specialised companies, Reply defines and develops business models enabled by the new models of AI, big data, cl...
Compliance Ranges Comparison
Telkomsel Enterprise
Reply
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Telkomsel Enterprise in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Reply in 2026.
Incident History - Telkomsel Enterprise (X = Date, Y = Severity)
Telkomsel Enterprise cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Reply (X = Date, Y = Severity)
Reply cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Telkomsel Enterprise
Reply
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.