Comparison Overview
Ingecal constructeur
Ingecal constructeur
10, Rue Ampère, Chassieu, Auvergne-Rhône-Alpes, 69680, FR
Last Update: 02/04/2026
Located close to Lyon, INGECAL, custom machine designer and manufacturer bring its expertise to provide specific technical and industrial equipment with roll to roll process. More than 20 years of experience in the high technology market, allow us to answer to challengi...
TK Elevator
E-Plus Straße 1, Düsseldorf, North Rhine-Westphalia, DE, 40472
Last Update: 14/09/2026
𝗪𝗲𝗹𝗰𝗼𝗺𝗲 𝘁𝗼 𝗧𝗞 𝗘𝗹𝗲𝘃𝗮𝘁𝗼𝗿 – 𝗪𝗵𝗲𝗿𝗲 𝗜𝗻𝗴𝗲𝗻𝘂𝗶𝘁𝘆 𝗘𝗹𝗲𝘃𝗮𝘁𝗲𝘀 𝗨𝗿𝗯𝗮𝗻 𝗟𝗶𝘃𝗶𝗻𝗴 Engineering pioneer. Global industry leader. TK Elevator draws on a legacy of firsts – from a groundbreaking vertical conveyor in 1890 – to evolve modern ...
Compliance Ranges Comparison
Ingecal constructeur
TK Elevator
Benchmark & Cyber Underwriting Signals
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Ingecal constructeur in 2026.
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for TK Elevator in 2026.
Incident History - Ingecal constructeur (X = Date, Y = Severity)
Ingecal constructeur cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TK Elevator (X = Date, Y = Severity)
TK Elevator cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Ingecal constructeur
TK Elevator
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.