Comparison Overview
Midea Italia

Midea Italia
Viale Luigi Bodio, 29/37, Milano, Lombardia, 20158, IT
Last Update: 14/02/2026
Parte di Midea Group, Midea Italia progetta elettrodomestici e soluzioni innovative per la casa, pensate per offrire un comfort senza precedenti. “Portare grandi innovazioni nella vita quotidiana" è la missione del Gruppo e la visione chiara dei suoi fondatori, che ...

TDK
2-5-1 Nihonbashi, Chuo-ku, 103-6128, JP
Last Update: 12/09/2026
TDK Corporation is a world leader in electronic solutions for the smart society based in Tokyo, Japan. Built on a foundation of material sciences mastery, TDK welcomes societal transformation by resolutely remaining at the forefront of technological evolution. It was es...
Compliance Ranges Comparison

Midea Italia







TDK






Benchmark & Cyber Underwriting Signals
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Midea Italia in 2026.
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for TDK in 2026.
Incident History - Midea Italia (X = Date, Y = Severity)
Midea Italia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TDK (X = Date, Y = Severity)
TDK cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Midea Italia

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