Comparison Overview
Workday Peakon Employee Voice

Workday Peakon Employee Voice
None, None, Pleasanton, California, US, None
Last Update: 01/04/2026
Workday Peakon Employee Voice empowers business leaders to deliver personalized employee experiences, during the moments that matter to build an inclusive, equitable culture for all. Thanks to its intelligent listening technology, it helps increase engagement, boost pro...

The Adecco Group
Bellerivestrasse 30, Zurich, 8008, CH
Last Update: 04/04/2026
The Adecco Group is a world leading talent company. Our purpose is making the future work for everyone. Through our three global business units - Adecco, Akkodis and LHH - across 60 countries, we enable sustainable and lifelong employability for individuals, deliver dig...
Compliance Ranges Comparison

Workday Peakon Employee Voice







The Adecco Group






Benchmark & Cyber Underwriting Signals
Incidents vs Human Resources Services Industry Avg (This Year)
No incidents recorded for Workday Peakon Employee Voice in 2026.
Incidents vs Human Resources Services Industry Avg (This Year)
No incidents recorded for The Adecco Group in 2026.
Incident History - Workday Peakon Employee Voice (X = Date, Y = Severity)
Workday Peakon Employee Voice cyber incidents detection timeline including parent company and subsidiaries.
Incident History - The Adecco Group (X = Date, Y = Severity)
The Adecco Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Workday Peakon Employee Voice

The Adecco Group
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.