Comparison Overview
Menard
Menard
22, Rue Jean Rostand, Orsay, 91400, FR
Last Update: 27/02/2026
Menard has been specialising in ground improvement works for the past 60 years. Thanks to a suite of technologies, we can optimise the properties of land to achieve the optimum geotechnical conditions to bear future surface structures. The innovative solutions applied b...
Hilti Group
Hilti Aktiengesellschaft, Schaan, 9494, LI
Last Update: 13/09/2026
Hilti stands for innovation and direct customer relationships. About 34,000 employees around the world, in more than 120 countries, contribute to making our customers’ work more productive, safer and more sustainable. We do this with our hardware, software and service o...
Compliance Ranges Comparison
Menard
Hilti Group
Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Menard in 2026.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Hilti Group in 2026.
Incident History - Menard (X = Date, Y = Severity)
Menard cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hilti Group (X = Date, Y = Severity)
Hilti Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Menard
Hilti Group
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.