Comparison Overview
Staples Facilities Solutions
Staples Facilities Solutions
undefined, Framingham, MA, undefined, US
Last Update: 16/12/2025
At Staples Facilities Solutions, we're committed to helping your business move forward. We're working around the clock to get you the products, services and information you need to navigate the new normal.
Sodexo
255 quai de la bataille de Stalingrad, 92866 Issy les Moulineaux Cedex 9, FR
Last Update: 14/09/2026
Founded in Marseille in 1966 by Pierre Bellon, Sodexo is the leader in Food and Services, shaping better everyday experiences at every moment in life: work, heal, learn and play. The Group stands out for its independence, its founding family shareholding and its respons...
Compliance Ranges Comparison
Staples Facilities Solutions
Sodexo
Benchmark & Cyber Underwriting Signals
Incidents vs Facilities Services Industry Avg (This Year)
No incidents recorded for Staples Facilities Solutions in 2026.
Incidents vs Facilities Services Industry Avg (This Year)
No incidents recorded for Sodexo in 2026.
Incident History - Staples Facilities Solutions (X = Date, Y = Severity)
Staples Facilities Solutions cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sodexo (X = Date, Y = Severity)
Sodexo cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Staples Facilities Solutions
Sodexo
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.