Comparison Overview
Legrand Hungary
Legrand Hungary
Gubacsi út 6, Budapest, Budapest, 1097, HU
Last Update: 09/11/2025
A Legrand az épületek villamos- és digitális adatátviteli infrastruktúráinak világszintű szakértője. A francia központú Legrand Csoport a termékeit minden földrészen értékesíti. 90 országban leányvállalattal van jelen, de összességében 180 országban áll képviselettel ve...
TE Connectivity
Galway, IE
Last Update: 11/09/2026
TE Connectivity plc (NYSE: TEL) is a global industrial technology leader creating a safer, sustainable, productive and connected future. As a trusted innovation partner, our broad range of connectivity and sensor solutions enable the distribution of power, signal and da...
Compliance Ranges Comparison
Legrand Hungary
TE Connectivity
Benchmark & Cyber Underwriting Signals
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Legrand Hungary in 2026.
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for TE Connectivity in 2026.
Incident History - Legrand Hungary (X = Date, Y = Severity)
Legrand Hungary cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TE Connectivity (X = Date, Y = Severity)
TE Connectivity cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Legrand Hungary
TE Connectivity
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.