Comparison Overview
OnLogic Customer Stories
OnLogic Customer Stories
35 Thompson Street, South Burlington, 05403, US
Last Update: 21/01/2026
See how OnLogic helped companies around the world solve their most complex hardware challenges and advance their ideas with powerful, reliable industrial computing solutions.
Western Digital
5601 Great Oaks Parkway, San Jose, CA, US, 95138
Last Update: 12/09/2026
At Western Digital, our vision is to unleash the power and value of data. For decades, we have been at the forefront of storage innovation, which fuels our mission to be the market leader in data storage, delivering solutions for now and the future. We are committed to ...
Compliance Ranges Comparison
OnLogic Customer Stories
Western Digital
Benchmark & Cyber Underwriting Signals
Incidents vs Computer Hardware Manufacturing Industry Avg (This Year)
No incidents recorded for OnLogic Customer Stories in 2026.
Incidents vs Computer Hardware Manufacturing Industry Avg (This Year)
No incidents recorded for Western Digital in 2026.
Incident History - OnLogic Customer Stories (X = Date, Y = Severity)
OnLogic Customer Stories cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Western Digital (X = Date, Y = Severity)
Western Digital cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
OnLogic Customer Stories
Western Digital
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.