Comparison Overview
Re/Max Realty Centre

Re/Max Realty Centre
US
Last Update: 08/03/2026

Colliers
1140 Bay St, Suite 4000, Toronto, Ontario, CA, M5S 2B4
Last Update: 27/05/2026
We are a global diversified professional services and investment management company operating through three industry-leading businesses: Commercial Real Estate, Engineering, and Investment Management. With greater than a 30-year track record of consistent growth and str...
Compliance Ranges Comparison

Re/Max Realty Centre







Colliers






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

Re/Max Realty Centre

Colliers
FAQ
Latest Global CVEs
An authenticated user with the read role may read limited amounts of uninitialized stack memory via specially-crafted issuances of the filemd5 command
The $_internalApplyOplogUpdate aggregation pipeline stage can be used to execute a document diff containing a malformed binary diff to return memory out-of-bounds or crash the server. $_internalApplyOplogUpdate can be executed by any authenticated user with access to the aggregate command.
An authorized user could trigger a server crash by running a query with a 2dsphere index on a field that stores a GeoJSON GeometryCollection containing a Polygon with a strict-winding CRS. Strict-winding polygons are intentionally unsupported for indexing, but the guard that rejects them does not inspect members of a GeometryCollection, allowing the unsafe path to be reached which ends with an ensuing null-pointer dereference.
The ldapQueryPassword parameter, when set through the runtime setParameter command, will log the new password to the mongod.log file in plain text.
An authenticated user can cause a MongoDB server to crash or return incorrect results by creating documents that interfere with internal metadata processing during query execution. This stems from insufficient separation between user-controlled document fields and internal metadata in certain execution paths.