Comparison Overview
Spike Reply Luxembourg

Spike Reply Luxembourg
21-25, Allée Scheffer, Luxembourg, L-2520 , LU
Last Update: 23/03/2026
Spike Reply is the company within the Reply Group focusing on cybersecurity and personal data protection. Its mission is to safeguard the values and privacy of people, companies and processes in order to support the growth of a global, sustainable digital world through ...

Appen
12131 113th Ave NE, Kirkland, 98034, US
Last Update: 01/04/2026
Appen has been a leader in AI training data for over 25 years, providing high-quality, diverse datasets that power the world's leading AI models. Our end-to-end platform, deep expertise, and scalable human-in-the-loop services enable AI innovators to build and optimize ...
Compliance Ranges Comparison

Spike Reply Luxembourg







Appen






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Spike Reply Luxembourg in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Appen in 2026.
Incident History - Spike Reply Luxembourg (X = Date, Y = Severity)
Spike Reply Luxembourg cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Appen (X = Date, Y = Severity)
Appen cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Spike Reply Luxembourg

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