Comparison Overview
Seco Tools
Seco Tools
Björnbacksvägen 10, Fagersta, Västmanlands Län, undefined, SE
Last Update: 05/04/2026
At Seco, we make tools, tech, and solutions for the most advanced manufacturing challenges on Earth. From our founding in Fagersta Sweden, to today’s global company, our business has always been made to measure, and built on trust. Combining cutting-edge, precision tool...
Wärtsilä
Hiililaiturinkuja 2, Helsinki, 00180, FI
Last Update: 13/09/2026
We are a global leader in innovative technologies and services shaping the decarbonisation of marine and energy. With approximately 6.9 billion euros in sales and 18,000 employees across 78 countries, the Wärtsilä strategy focuses on helping customers to continuously im...
Compliance Ranges Comparison
Seco Tools
Wärtsilä
Benchmark & Cyber Underwriting Signals
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Seco Tools in 2026.
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Wärtsilä in 2026.
Incident History - Seco Tools (X = Date, Y = Severity)
Seco Tools cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Wärtsilä (X = Date, Y = Severity)
Wärtsilä cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Seco Tools
Wärtsilä
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.