Comparison Overview
PwC Czech Republic

PwC Czech Republic
Hvezdova 1734/2c, Prague, 140 00, CZ
Last Update: 06/03/2026
At PwC, our purpose is to build trust in society and solve important problems. We’re a network of firms in 158 countries with more than 250,000 people who are committed to delivering quality in assurance, advisory and tax services. PwC Czech Republic In 1990, Coopers ...

Publicis Sapient
40 Water St, Boston, Massachusetts, US, 02109
Last Update: 02/04/2026
Publicis Sapient is a technology company that provides enterprise AI platforms and services. With over 30 years of digital business transformation experience, we enable enterprise clients to transform how they operate and serve their customers, unlocking new value and e...
Compliance Ranges Comparison

PwC Czech Republic







Publicis Sapient






Benchmark & Cyber Underwriting Signals
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for PwC Czech Republic in 2026.
Incidents vs Business Consulting and Services Industry Avg (This Year)
Publicis Sapient has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - PwC Czech Republic (X = Date, Y = Severity)
PwC Czech Republic cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Publicis Sapient (X = Date, Y = Severity)
Publicis Sapient cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

PwC Czech Republic

Publicis Sapient
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.