Comparison Overview
Nidec Corporation Global

Nidec Corporation Global
久世殿城町338, 京都市南区, 6018205, JP
Last Update: 30/06/2026
Kyoto, Japan

WEG
Avenida Pref. Waldemar Grubba, 3300, Jaraguá do Sul, 89256-900, BR
Last Update: 12/09/2026
Founded in 1961, WEG is a global electro-electronic equipment company, operating in the capital goods sector a with focus on electric motors, gearboxes and drives and controls, energy generation and transformers, electrification products and systems, automation and digi...
Compliance Ranges Comparison

Nidec Corporation Global







WEG






Benchmark & Cyber Underwriting Signals
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
Nidec Corporation Global has 51.69% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for WEG in 2026.
Incident History - Nidec Corporation Global (X = Date, Y = Severity)
Nidec Corporation Global cyber incidents detection timeline including parent company and subsidiaries.
Incident History - WEG (X = Date, Y = Severity)
WEG cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Nidec Corporation Global

WEG
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.