Comparison Overview
Nidec Leroy-Somer
Nidec Leroy-Somer
Boulevard Marcellin Leroy, ANGOULEME, 16015, FR
Last Update: 04/03/2026
LEROY-SOMER® is one of the oldest and most respected brands in the motor industry. Since 1909, our brand has stood for exceptional product reliability and performance. Today, it is recognized worldwide as the mark of technological innovation and energy efficiency in ind...
Flex
12455 Research Blvd, Austin, Texas, US, 78759
Last Update: 13/09/2026
Flex (Reg. No. 199002645H) is the global manufacturing partner of choice that helps leading brands design, build, and manage products that improve the world. For more information, visit flex.com. We love to hear your thoughts, comments and ideas so feel free to like, s...
Compliance Ranges Comparison
Nidec Leroy-Somer
Flex
Benchmark & Cyber Underwriting Signals
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Nidec Leroy-Somer in 2026.
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Flex in 2026.
Incident History - Nidec Leroy-Somer (X = Date, Y = Severity)
Nidec Leroy-Somer cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Flex (X = Date, Y = Severity)
Flex cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Nidec Leroy-Somer
Flex
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.