Comparison Overview
Entrepose Contracting

Entrepose Contracting
Archipel VINCI - 1973 Bd de la Défense, Nanterre, 92000, FR
Last Update: 27/03/2026
Entrepose Contracting, a subsidiary of VINCI Construction Grands Projets, designs and delivers critical energy infrastructure for the storage, treatment, and transportation of conventional and low-carbon energies. 🔹 Drawing on 60+ years of cryogenic engineering and he...

Equinor
Forusbeen 50, Stavanger, Rogaland, NO, 4035
Last Update: 10/09/2026
We're Equinor, an international energy company with a proud history. Formerly Statoil, we are 20,000 committed colleagues developing oil, gas, wind and solar energy in more than 30 countries worldwide. We’re the largest operator in Norway, among the world’s largest offs...
Compliance Ranges Comparison

Entrepose Contracting







Equinor






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

Entrepose Contracting

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