Comparison Overview
trivago

trivago
Kesselstraße 5, Düsseldorf, North Rhine-Westphalia, DE, 40221
Last Update: 02/04/2026
When travelers are searching for a hotel, we want the obvious choice to be trivago! By comparing prices from major booking sites, we're making it easy for people to find hotels they want at a price they’ll love. In the lively city of Düsseldorf, we seize opportunities t...

PayPal
2211 North First Street, San Jose, CA, US, 95131
Last Update: 26/06/2026
We're championing possibilities for all by making money fast, easy, and more enjoyable. Our hope is to unlock opportunities for people in their everyday lives and empower the millions of people and businesses around the world who trust, rely, and use PayPal every day. ...
Compliance Ranges Comparison

trivago







PayPal






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for trivago in 2026.
Incidents vs Software Development Industry Avg (This Year)
PayPal has 482.52% more incidents than the average of all companies with at least one recorded incident.
Incident History - trivago (X = Date, Y = Severity)
trivago cyber incidents detection timeline including parent company and subsidiaries.
Incident History - PayPal (X = Date, Y = Severity)
PayPal cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

trivago

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