Comparison Overview
SETAO
SETAO
01 BP 925 Abidjan, Abidjan, 22 rue des foreurs Zone 3 , 00225, CI
Last Update: 29/11/2025
𝐁𝐨𝐮𝐲𝐠𝐮𝐞𝐬 𝐂𝐨𝐧𝐬𝐭𝐫𝐮𝐜𝐭𝐢𝐨𝐧 : 𝐁𝐚̂𝐭𝐢𝐫 𝐩𝐨𝐮𝐫 𝐥𝐚 𝐯𝐢𝐞 Chez Bouygues Construction, nous sommes 32 500 collaborateurs à travers le monde, tous animés par la plus grande et la plus enthousiasmante des responsabilités : bâtir pour la vie. Pour nos cli...
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
SETAO
Fluor Corporation
Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for SETAO in 2026.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Fluor Corporation in 2026.
Incident History - SETAO (X = Date, Y = Severity)
SETAO 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
SETAO
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.