Comparison Overview
METALTECH & AUTOMEX
METALTECH & AUTOMEX
Lingkaran SV Sunway Velocity, Kuala Lumpur, 55100, MY
Last Update: 30/03/2026
METALTECH & AUTOMEX pioneers the growth of the metalworking, machinery, robotics, and automation industry in Malaysia - being the first dedicated business event to represent various sectors of the manufacturing industry including electrical and electronics, automotive, ...
ANDRITZ
Stattegger Strasse 18, Graz, 8045, AT
Last Update: 01/04/2026
ANDRITZ is an international technology group based in Austria. The company offers a broad portfolio of innovative plants, equipment, systems, services and digital solutions for a wide range of industries and end markets. Sustainability is an integral part of the compa...
Compliance Ranges Comparison
METALTECH & AUTOMEX
ANDRITZ
Benchmark & Cyber Underwriting Signals
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for METALTECH & AUTOMEX in 2026.
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for ANDRITZ in 2026.
Incident History - METALTECH & AUTOMEX (X = Date, Y = Severity)
METALTECH & AUTOMEX cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ANDRITZ (X = Date, Y = Severity)
ANDRITZ cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
METALTECH & AUTOMEX
ANDRITZ
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.