Comparison Overview
Clear Title Group
Clear Title Group
1111 Lincoln Rd, Miami Beach, 33139, US
Last Update: 10/12/2025
At Clear Title Group, we believe that high-quality service isn't everything; it’s the only thing. That’s why we focus on providing our clients with an unparalleled real estate title and closing experience. Our service is tailored to meet each of our client’s needs and t...
Compass
110 Fifth Avenue, New York, 10011, US
Last Update: 14/09/2026
Compass is a real estate technology company with a powerful end-to-end platform that supports the entire buying and selling workflow. We deliver an incomparable experience to both agents and their clients all in service of the Compass mission: to help everyone find thei...
Compliance Ranges Comparison
Clear Title Group
Compass
Benchmark & Cyber Underwriting Signals
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for Clear Title Group in 2026.
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for Compass in 2026.
Incident History - Clear Title Group (X = Date, Y = Severity)
Clear Title Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Compass (X = Date, Y = Severity)
Compass cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Clear Title Group
Compass
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.