Comparison Overview
Peregrine Group
Peregrine Group
150 South Wacker Drive, Chicago, 60606, US
Last Update: 30/03/2026
The Principals of Peregrine Group have conducted nationwide searches for all levels and functions of real estate professionals, as well as all property types and capital sources. Clients range from growth-oriented entrepreneurs and developers to institutional investors,...
REMAX
5075 S. Syracuse St., Denver, 80237, US
Last Update: 01/04/2026
As one of the leading global real estate franchisors, RE/MAX, LLC is a subsidiary of RE/MAX Holdings (NYSE: RMAX) with more than 140,000 agents in almost 9,000 offices and a presence in more than 110 countries and territories. Nobody in the world sells more real estat...
Compliance Ranges Comparison
Peregrine Group
REMAX
Benchmark & Cyber Underwriting Signals
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for Peregrine Group in 2026.
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for REMAX in 2026.
Incident History - Peregrine Group (X = Date, Y = Severity)
Peregrine Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - REMAX (X = Date, Y = Severity)
REMAX cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Peregrine Group
REMAX
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.