Comparison Overview
Utilihive
Utilihive
Storgata 1, Oslo, 0155, NO
Last Update: 04/03/2026
Utilihive is a revolutionary digital integration hub and domain specific integration Platform as a Service (iPaaS). The platform is able to connect to all your existing and future systems with prebuilt connectors and data flows to support common business processes and u...
PT PLN (Persero)
Jl. Trunojoyo Blok M I/135, Jakarta Selatan, 12160, ID
Last Update: 04/09/2026
Indonesia State Electricity Corporation PLN has a long history in electricity industry of Indonesia. As the sole provider of electricity in Indonesia, PLN is striving to increase quality of services to all Indonesian. In 1972, in accordance with Government Regulation N...
Compliance Ranges Comparison
Utilihive
PT PLN (Persero)
Benchmark & Cyber Underwriting Signals
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for Utilihive in 2026.
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for PT PLN (Persero) in 2026.
Incident History - Utilihive (X = Date, Y = Severity)
Utilihive cyber incidents detection timeline including parent company and subsidiaries.
Incident History - PT PLN (Persero) (X = Date, Y = Severity)
PT PLN (Persero) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Utilihive
PT PLN (Persero)
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.