Comparison Overview
Avnet Displays
Avnet Displays
Industriestraße, Stutensee, 76297, DE
Last Update: 26/12/2025
We design and build displays and touch screens for businesses, and we love doing it. Our in-house team works directly with businesses to solve all the challenges of integrating a display into a product design, from tiny wearables to massive outdoor screens. We design, b...
Cox Enterprises
6305 Peachtree Dunwoody Rd, Atlanta, 30328, US
Last Update: 06/09/2026
Thousands of employees, one goal: empower people today to build a better future for the next generation. How do we do that? By disrupting industries. By treating our employees as our most important resource. By improving the quality of life in our communities and by pro...
Compliance Ranges Comparison
Avnet Displays
Cox Enterprises
Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Media Industry Avg (This Year)
No incidents recorded for Avnet Displays in 2026.
Incidents vs Technology, Information and Media Industry Avg (This Year)
No incidents recorded for Cox Enterprises in 2026.
Incident History - Avnet Displays (X = Date, Y = Severity)
Avnet Displays cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Cox Enterprises (X = Date, Y = Severity)
Cox Enterprises cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Avnet Displays
Cox Enterprises
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.