Comparison Overview
Motion Automation Intelligence
Motion Automation Intelligence
1605 Alton Rd, Birmingham, 35210, US
Last Update: 01/03/2026
Motion Ai brings together the leading high-tech automation solution providers for industrial automation across the United States. The expertise found in this group includes emerging automation technologies with focused disciplines in robotics, motion control, machine vi...
ABB
Affolternstrasse 44, Zurich, 8050, CH
Last Update: 10/09/2026
ABB is a technology leader in electrification and automation, enabling a more sustainable and resource-efficient future. The company’s solutions connect engineering know-how and software to optimize how things are manufactured, moved, powered and operated. Building on o...
Compliance Ranges Comparison
Motion Automation Intelligence
ABB
Benchmark & Cyber Underwriting Signals
Incidents vs Automation Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Motion Automation Intelligence in 2026.
Incidents vs Automation Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for ABB in 2026.
Incident History - Motion Automation Intelligence (X = Date, Y = Severity)
Motion Automation Intelligence cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ABB (X = Date, Y = Severity)
ABB cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Motion Automation Intelligence
ABB
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.