Comparison Overview
cxLoyalty

cxLoyalty
High Ridge Park, Building 6, Floor C-2, Stamford, Connecticut, US, 06905
Last Update: 02/12/2025
As part of our consolidation into Chase Travel, the client loyalty programs we have offered for decades are now part of Chase Travel Corporate Solution’s suite of services. Follow along on @chase travel corporate solutions, our new home on LinkedIn. Interested in how h...

Costa Crociere S.p.A.
Piazza Piccapietra 48, Genova, IT, 16121
Last Update: 30/03/2026
Costa belongs to the Carnival Corporation & plc Group, listed on the London and New York stock exchanges, the largest cruise company in the world. Costa, the only Italian cruise company flying the Italian flag, has been sailing the world’s seas for more than 75 years,...
Compliance Ranges Comparison

cxLoyalty







Costa Crociere S.p.A.






Benchmark & Cyber Underwriting Signals
Incidents vs Travel Arrangements Industry Avg (This Year)
No incidents recorded for cxLoyalty in 2026.
Incidents vs Travel Arrangements Industry Avg (This Year)
No incidents recorded for Costa Crociere S.p.A. in 2026.
Incident History - cxLoyalty (X = Date, Y = Severity)
cxLoyalty cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Costa Crociere S.p.A. (X = Date, Y = Severity)
Costa Crociere S.p.A. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

cxLoyalty

Costa Crociere S.p.A.
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.