Comparison Overview
Compass Digital
Compass Digital
undefined, Mississauga, ON, undefined, CA
Last Update: 06/03/2026
We’re the digital transformation and innovation experts at Compass Group North America. We use technology to empower operators, enhance the customer experience, and identify business opportunities in food, services, and hospitality.
Zebra Technologies
3 Overlook Point, Lincolnshire, 60069, US
Last Update: 09/09/2026
Zebra provides the foundation for intelligent operations with an award-winning portfolio of connected frontline, asset visibility and automation solutions. Organizations globally across retail, manufacturing, transportation, logistics, healthcare, and other industries r...
Compliance Ranges Comparison
Compass Digital
Zebra Technologies
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Compass Digital in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Zebra Technologies in 2026.
Incident History - Compass Digital (X = Date, Y = Severity)
Compass Digital cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Zebra Technologies (X = Date, Y = Severity)
Zebra Technologies cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Compass Digital
Zebra Technologies
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.