Comparison Overview
WorkFlo by OYO
WorkFlo by OYO
58 Sector Road, Gurgaon, Haryana, undefined, IN
Last Update: 02/12/2025
efficient, quality and vibrant WorkSpaces for teams of any size. Ready to move as well as customised WorkSpaces
Anywhere Real Estate Inc.
Madison, New Jersey, US
Last Update: 31/03/2026
Anywhere Real Estate Inc. (NYSE: HOUS) is moving the real estate industry to what's next. A leader of integrated residential real estate services, Anywhere includes franchise, brokerage, relocation, and title and settlement businesses, as well as mortgage and title insu...
Compliance Ranges Comparison
WorkFlo by OYO
Anywhere Real Estate Inc.
Benchmark & Cyber Underwriting Signals
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for WorkFlo by OYO in 2026.
Incidents vs Real Estate Industry Avg (This Year)
Anywhere Real Estate Inc. has 4.76% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - WorkFlo by OYO (X = Date, Y = Severity)
WorkFlo by OYO cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Anywhere Real Estate Inc. (X = Date, Y = Severity)
Anywhere Real Estate Inc. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
WorkFlo by OYO
Anywhere Real Estate Inc.
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: *.*.