Comparison Overview
Staples
Staples
500 Staples Drive, Framingham, 01702, US
Last Update: 01/04/2026
For nearly 40 years, Staples has been a trusted leader in delivering end-to-end workplace solutions for consumers and businesses of all sizes across a broad range of industries. The company provides a comprehensive portfolio of products, strategic solutions, and service...
Office Depot
6600 N. Military Trail, Boca Raton, 33496, US
Last Update: 01/04/2026
Office Depot, LLC, an operating company of The ODP Corporation, is a leading specialty retailer providing innovative products and services delivered through a fully integrated omnichannel platform of Office Depot and OfficeMax retail stores and an award-winning online p...
Compliance Ranges Comparison
Staples
Office Depot
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Office Equipment Industry Avg (This Year)
Staples has 33.33% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Retail Office Equipment Industry Avg (This Year)
No incidents recorded for Office Depot in 2026.
Incident History - Staples (X = Date, Y = Severity)
Staples cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Office Depot (X = Date, Y = Severity)
Office Depot cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Staples
Office Depot
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.