Comparison Overview
Workthere

Workthere
33 Margaret Street, London, GB, W1G 0JD
Last Update: 27/11/2025
Our team of global experts provide you with local market insights and data driven advice to enable you to make better decisions when it comes to flexible workspace. If you're looking for a new office, or want to let your space or have it managed, we can help. Our trus...

Compass
110 Fifth Avenue, New York, 10011, US
Last Update: 01/04/2026
Compass is a real estate technology company with a powerful end-to-end platform that supports the entire buying and selling workflow. We deliver an incomparable experience to both agents and their clients all in service of the Compass mission: to help everyone find thei...
Compliance Ranges Comparison

Workthere







Compass






Benchmark & Cyber Underwriting Signals
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for Workthere in 2026.
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for Compass in 2026.
Incident History - Workthere (X = Date, Y = Severity)
Workthere cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Compass (X = Date, Y = Severity)
Compass cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Workthere

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