Comparison Overview
NMDC Energy

NMDC Energy
Mussafah Industrial Area, Zone 6, Street 7, Plot 71, Abu Dhabi, AE
Last Update: 04/04/2026
Established in 1973, NMDC Energy (formerly NPCC) is a leading EPC company working in the energy sector. From our base in Abu Dhabi we provide a wide range of EPC services to companies including ADMA-OPCO, ZADCO, ARAMCO and ONGC. With offices around the world, the large...

PETRONAS
Kuala Lumpur, 50088, MY
Last Update: 07/09/2026
Petroliam Nasional Berhad (PETRONAS) is a leading global energy company committed to powering society’s progress in a responsible and sustainable manner. With close to 50,000 employees and a global reach spanning over 100 countries, we are ranked among the world’s large...
Compliance Ranges Comparison

NMDC Energy







PETRONAS






Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for NMDC Energy in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for PETRONAS in 2026.
Incident History - NMDC Energy (X = Date, Y = Severity)
NMDC Energy cyber incidents detection timeline including parent company and subsidiaries.
Incident History - PETRONAS (X = Date, Y = Severity)
PETRONAS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

NMDC Energy

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