Comparison Overview
former Hilti Russia
former Hilti Russia
undefined, none, undefined, undefined, RU
Last Update: 06/04/2026
Schaan (FL) - August 5, 2024 After more than 30 years of operations in Russia and more than 15 years in Belarus, the Hilti Group has decided to exit both markets. Since 2022 the Hilti Group has significantly ramped down its operations in and ceased all exports to Russ...
NCC
Herrjärva Torg 4, Stockholm, Solna, SE, 170 67
Last Update: 14/09/2026
NCC is one of the leading construction companies in the Nordics. Based on its expertise in managing complex construction processes, NCC contributes to a positive impact of construction for its customers and society. NCC is one of the largest players in the Nordic cons...
Compliance Ranges Comparison
former Hilti Russia
NCC
Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for former Hilti Russia in 2026.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for NCC in 2026.
Incident History - former Hilti Russia (X = Date, Y = Severity)
former Hilti Russia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - NCC (X = Date, Y = Severity)
NCC cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
former Hilti Russia
NCC
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.