Comparison Overview
Larox
Larox
undefined, Lappeenranta, undefined, 53900, FI
Last Update: 27/12/2025
Larox develops, designs, manufactures and supplies filtration solutions and is a leading technology company in its field. Larox is a full service filtration solution provider in solid and liquid separation. Comprehensive aftermarket services throughout the lifespan of t...
Valmet
Keilasatama 5, Espoo, FI, FI, 02150
Last Update: 14/09/2026
Valmet is a global technology leader serving process industries. We work together with our customers throughout the entire lifecycle, delivering cutting-edge technologies and services as well as mission-critical automation and flow control solutions. Backed by more than...
Compliance Ranges Comparison
Larox
Valmet
Benchmark & Cyber Underwriting Signals
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Larox in 2026.
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Valmet in 2026.
Incident History - Larox (X = Date, Y = Severity)
Larox cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Valmet (X = Date, Y = Severity)
Valmet cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Larox
Valmet
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.