Comparison Overview
Ilapak Packaging Machinery
Ilapak Packaging Machinery
PO BOX 756, Grancia-Lugano, 6916, CH
Last Update: 10/12/2025
As one of the world’s leading manufacturers, IMA ILAPAK, with its vast range of machinery, can satisfy virtually all form, fill and seal packaging requirements: modified atmosphere, horizontal and vertical packaging, product handling, automation and cartoning. ILAPAK’s...
Konecranes
P.O. Box 661, Koneenkatu 8, Hyvinkaa, FI, 05801
Last Update: 14/09/2026
Konecranes is a global leader in material handling solutions, serving a broad range of customers across multiple industries. We consistently set the industry benchmark, from everyday improvements to the breakthroughs at moments that matter most, because we know we can a...
Compliance Ranges Comparison
Ilapak Packaging Machinery
Konecranes
Benchmark & Cyber Underwriting Signals
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Ilapak Packaging Machinery in 2026.
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Konecranes in 2026.
Incident History - Ilapak Packaging Machinery (X = Date, Y = Severity)
Ilapak Packaging Machinery cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Konecranes (X = Date, Y = Severity)
Konecranes cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Ilapak Packaging Machinery
Konecranes
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.