Comparison Overview
CT REIT
CT REIT
2180 Yonge St, Toronto, M4P, CA
Last Update: 07/12/2025
CT Real Estate Investment Trust (CT REIT) is an unincorporated, closed end real estate investment trust formed to own income producing commercial properties primarily located in Canada. Its portfolio is comprised of over 370 properties totaling approximately 30 million ...
FirstService Residential
1855 Griffin Road, Suite A-330, Dania Beach, FL, US, 33004
Last Update: 14/09/2026
FirstService Residential is simplifying property management. Its hospitality-minded teams serve residential communities across the United States and Canada. The organization partners with boards, owners, and developers to enhance every property's value and every residen...
Compliance Ranges Comparison
CT REIT
FirstService Residential
Benchmark & Cyber Underwriting Signals
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for CT REIT in 2026.
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for FirstService Residential in 2026.
Incident History - CT REIT (X = Date, Y = Severity)
CT REIT cyber incidents detection timeline including parent company and subsidiaries.
Incident History - FirstService Residential (X = Date, Y = Severity)
FirstService Residential cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
CT REIT
FirstService Residential
FAQ
Latest Global CVEs
vLLM through 0.29.0 fails to properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/push_worker.py#L162-L181
- https://github.com/vllm-project/vllm/pull/55677
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-rejected-requests
redis-parser through 3.0.0 contains a denial of service vulnerability in the RESP protocol parser that allows malicious Redis endpoints to crash the client process through unbounded recursion on nested arrays. Attackers can send crafted RESP byte streams with repeated array headers that exhaust the V8 call stack, causing an uncaught RangeError that terminates the Node.js process without triggering error handling callbacks.
- https://github.com/NodeRedis/node-redis-parser
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L204-L213
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L291-L306
- https://github.com/redis/ioredis/issues/2108
- https://www.vulncheck.com/advisories/redis-parser-through-3.0.0-denial-of-service-via-unbounded-recursion
Improper neutralization of special elements in output used by a downstream component ('injection') in Azure Cosmos DB allows an authorized attacker to elevate privileges over a network.
Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.