Comparison Overview
Brave

Brave
580 Howard St., San Francisco, 94105, US
Last Update: 12/06/2026
Brave is on a mission to build a user-first Web. Starting with our flagship browser and search engine, Brave shields users from the creepy ads and trackers that follow you across the web. Our browser has more than 109 million users and our search engine delivers over 2 ...

Cimpress
Xerox Technology Park, Dundalk, A91 H9N9, IE
Last Update: 03/04/2026
Cimpress plc (Nasdaq: CMPR) invests in and builds customer-focused, entrepreneurial, mass-customization businesses for the long term. Mass customization is a competitive strategy which seeks to produce goods and services to meet individual customer needs with near mass ...
Compliance Ranges Comparison

Brave







Cimpress






Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
Brave has 145.4% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Cimpress in 2026.
Incident History - Brave (X = Date, Y = Severity)
Brave cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Cimpress (X = Date, Y = Severity)
Cimpress cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Brave

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