Comparison Overview
MR PORTER

MR PORTER
1 The Village Offices, London, London, GB, W12 7GF
Last Update: 27/02/2026
MR PORTER is the men’s luxury style destination. Since 2011, it has offered customers a curated assortment of fashion, fine watches, grooming and lifestyle products from the world’s most coveted designers. It delivers exceptional quality with private label, Mr P., and m...

Tupperware
320 Park Avenue, 26th Floor, New York, NY, US, 10022
Last Update: 02/04/2026
Founded in 1946, Tupperware's signature container created the modern food storage category that revolutionized the way the world stores, serves and prepares food. Today, we continue to innovate for the benefit of people and our planet by designing innovative, functional...
Compliance Ranges Comparison

MR PORTER







Tupperware






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for MR PORTER in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Tupperware in 2026.
Incident History - MR PORTER (X = Date, Y = Severity)
MR PORTER cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Tupperware (X = Date, Y = Severity)
Tupperware cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

MR PORTER

Tupperware
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.