Comparison Overview
VINCI Construction
VINCI Construction
1973, Boulevard de la Défense, Nanterre, 92000, FR
Last Update: 16/09/2026
Premier groupe français et acteur mondial de premier plan de la construction, VINCI Construction réunit plus de 830 entreprises et près de 69000 collaborateurs dans une centaine de pays. Ses expertises s’étendent à l’ensemble des métiers du bâtiment, du génie civil, et ...
Tata Projects
14th - 15th Floor, Cignus, Mumbai, 400087, IN
Last Update: 14/09/2026
Tata Projects is one of the most admired Technology led Engineering, Procurement and Construction (EPC) companies in India. We have expertise in providing sustainable solutions in the execution of large and complex urban and industrial infrastructure projects while also...
Compliance Ranges Comparison
VINCI Construction
Tata Projects
Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for VINCI Construction in 2026.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Tata Projects in 2026.
Incident History - VINCI Construction (X = Date, Y = Severity)
VINCI Construction cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Tata Projects (X = Date, Y = Severity)
Tata Projects cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
VINCI Construction
Tata Projects
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.