Comparison Overview
RS DACH
RS DACH
Mainzer Landstraße 180, Atrium Plaza, Frankfurt am Main, Hessen, DE, 60327
Last Update: 15/02/2026
RS ist eine Handelsmarke der RS Group plc. Als Anbieter von Produkt- und Servicelösungen unterstützen wir unsere Kunden dabei, sichere und nachhaltige Industrieanlagen und -betriebe zu entwerfen, zu warten, zu reparieren und zu betreiben. Wir liefern mehr als 800.000 In...
Wesco
225 W Station Square Dr, Pittsburgh, Pennsylvania, US, 15219
Last Update: 12/08/2026
At Wesco, we believe life should run smoothly. As a leading provider of business-to-business distribution, logistics services and supply chain solutions, we create a world that you can depend on. Harnessing 100 years of ingenuity and expertise, we increase profitability...
Compliance Ranges Comparison
RS DACH
Wesco
Benchmark & Cyber Underwriting Signals
Incidents vs Wholesale Industry Avg (This Year)
No incidents recorded for RS DACH in 2026.
Incidents vs Wholesale Industry Avg (This Year)
Wesco has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - RS DACH (X = Date, Y = Severity)
RS DACH cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Wesco (X = Date, Y = Severity)
Wesco cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
RS DACH
Wesco
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.