Comparison Overview
Retail Space Solutions

Retail Space Solutions
2727 West Good Hope Road, Milwaukee, 53209, US
Last Update: 07/12/2025
Retail Space Solutions – a Marmon/Berkshire Hathaway Company – designs, develops and produces a premium line of retail merchandising solutions that enhance product displays, positively impact the in-store shopping experience, improve labor efficiency, and deliver ROI th...

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...
Compliance Ranges Comparison

Retail Space Solutions







Staples






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Office Equipment Industry Avg (This Year)
No incidents recorded for Retail Space Solutions in 2026.
Incidents vs Retail Office Equipment Industry Avg (This Year)
Staples has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Retail Space Solutions (X = Date, Y = Severity)
Retail Space Solutions cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Staples (X = Date, Y = Severity)
Staples cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Retail Space Solutions

Staples
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.