Comparison Overview
JLL Value and Risk Advisory
JLL Value and Risk Advisory
200 E Randolph St, Chicago, 60601, US
Last Update: 07/03/2026
JLL Value and Risk Advisory is the essential guide to the changing face of real estate values and risk. Our expert value and risk specialists are here to help investors and lenders identify, mitigate and monitor risk, and optimize real estate values across all sectors ...
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
JLL Value and Risk Advisory
Compass
Benchmark & Cyber Underwriting Signals
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for JLL Value and Risk Advisory in 2026.
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for Compass in 2026.
Incident History - JLL Value and Risk Advisory (X = Date, Y = Severity)
JLL Value and Risk Advisory 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
JLL Value and Risk Advisory
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.