Comparison Overview
Innovative Construction Group
Innovative Construction Group
5216 Shad Rd, None, Jacksonville, Florida, US, None
Last Update: 20/04/2026
At ICG, We are Building the Future with a Passionate Pursuit of Excellence in Construction. What that means at ICG: • Adhere to the highest ethical and moral standards, honesty and integrity. • Foster a positive, enjoyable work environment where associates grow into n...
Holcim
Grafenauweg 10, Zug, CH, 6300
Last Update: 17/09/2026
Holcim is the leading partner for sustainable construction with net sales of CHF 15.7 billion in 2025, creating value across the built environment from infrastructure and industry to buildings. We have more than 45 000 employees in 43 attractive markets – across Europ...
Compliance Ranges Comparison
Innovative Construction Group
Holcim
Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Innovative Construction Group in 2026.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Holcim in 2026.
Incident History - Innovative Construction Group (X = Date, Y = Severity)
Innovative Construction Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Holcim (X = Date, Y = Severity)
Holcim cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Innovative Construction Group
Holcim
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.