Comparison Overview
Zest Reply

Zest Reply
Gulledelle 96, St-Lambrechts-Woluwe, 1200, BE
Last Update: 20/12/2025
Zest Reply was born with the ambition to help customers deploy Enterprise levels Generative AI Solutions with a focus on Customer Engagement, Compliance Reporting and applications to Software Development.

Mastercard
2000 Purchase St, Purchase, NY, US, 10577
Last Update: 28/06/2026
Mastercard powers economies and empowers people in 200+ countries and territories worldwide. Together with our customers, we’re building a sustainable economy where everyone can prosper. We support a wide range of digital payments choices, making transactions secure, si...
Compliance Ranges Comparison

Zest Reply







Mastercard






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

Zest Reply

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