Comparison Overview
Butter (Subscriptions Hub)

Butter (Subscriptions Hub)
88 Queens Quay W, Toronto, CA
Last Update: 30/03/2026
Our mission at Butter is to help you get the most of your memberships and subscriptions. Things like Netflix, Spotify, Dropbox, Amazon Prime, and Costco, just to name a few! We start off by helping you track and manage your subscriptions. As we get to know you better, ...

Booking Holdings (NASDAQ: BKNG)
800 Connecticut Avenue, Norwalk, 06854, US
Last Update: 09/08/2026
Booking Holdings is the world’s leading provider of online travel & related services, provided to consumers and local partners in more than 220 countries and territories through six primary consumer-facing brands: Booking.com, Priceline, Agoda, Rentalcars.com, KAYAK and...
Compliance Ranges Comparison

Butter (Subscriptions Hub)







Booking Holdings (NASDAQ: BKNG)






Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Butter (Subscriptions Hub) in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
Booking Holdings (NASDAQ: BKNG) has 94.17% more incidents than the average of all companies with at least one recorded incident.
Incident History - Butter (Subscriptions Hub) (X = Date, Y = Severity)
Butter (Subscriptions Hub) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Booking Holdings (NASDAQ: BKNG) (X = Date, Y = Severity)
Booking Holdings (NASDAQ: BKNG) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Butter (Subscriptions Hub)

Booking Holdings (NASDAQ: BKNG)
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.