Comparison Overview
Ashford Inc.

Ashford Inc.
14185 Dallas Pkwy, None, Dallas, Texas, US, None
Last Update: 30/03/2026
Ashford Inc. is an alternative asset management company with a portfolio of strategic operating businesses that provide global asset management, investment management and related services to the real estate and hospitality sectors. Ashford's principals have a long track...

Weichert, Realtors
1625 Rt. 10 East, Morris Plains, 07950, US
Last Update: 01/04/2026
Since 1969, Weichert Realtors has grown from a single office into one of the nation's leading providers of real estate and related services. Their success is rooted in their customer-first philosophy, making every organizational decision based on building trust and sust...
Compliance Ranges Comparison

Ashford Inc.







Weichert, Realtors






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

Ashford Inc.

Weichert, Realtors
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: *.*.