Comparison Overview
Topec International B.V.
Topec International B.V.
Ketelweg 28, Papendrecht, 3356 LE, NL
Last Update: 14/02/2026
The demand for energy continues to grow, but is also becoming increasingly expensive at the same time. As a result, the possibility to generate electrical energy independently is not only useful in terms of reliability (emergency power), but also for reducing energy cos...
Parker Hannifin
6035 Parkland Blvd, Cleveland, 44124, US
Last Update: 08/09/2026
Parker Hannifin is a Fortune 250 global leader in motion and control technologies. Guided by our purpose—“Enabling Engineering Breakthroughs that Lead to a Better Tomorrow”—we help customers solve complex challenges through expertise in electromechanical systems, filtra...
Compliance Ranges Comparison
Topec International B.V.
Parker Hannifin
Benchmark & Cyber Underwriting Signals
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Topec International B.V. in 2026.
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Parker Hannifin in 2026.
Incident History - Topec International B.V. (X = Date, Y = Severity)
Topec International B.V. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Parker Hannifin (X = Date, Y = Severity)
Parker Hannifin cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Topec International B.V.
Parker Hannifin
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.