Comparison Overview
Equans Data Centers

Equans Data Centers
N/A
Last Update: 29/03/2026
We are a strategic data center partner delivering every aspect of general contractor design, build, and commissioning for major data centers across Europe to provide new build, fit-out, complex retrofit, and upgrade through one point of contact. Leveraging decades of e...

Fluor Corporation
6700 Las Colinas Blvd., Irving, 75039, US
Last Update: 14/09/2026
Fluor Corporation is a global engineering, procurement and construction company. We work with leaders in the energy, infrastructure, life sciences, advanced technologies, mining and metals industries, as well as government agencies, to build a better world. Since our f...
Compliance Ranges Comparison

Equans Data Centers







Fluor Corporation






Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Equans Data Centers in 2026.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Fluor Corporation in 2026.
Incident History - Equans Data Centers (X = Date, Y = Severity)
Equans Data Centers cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Fluor Corporation (X = Date, Y = Severity)
Fluor Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Equans Data Centers

Fluor Corporation
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.