Comparison Overview
Swire Properties
Swire Properties
N/A
Last Update: 05/02/2026
Established in Hong Kong in 1972, Swire Properties is a leading developer, owner and operator of mixed-use, principally commercial properties in Hong Kong and the Chinese Mainland, with a well-established record of creating long-term value by transforming urban areas. O...
Keller Williams Realty, LLC
Suite 400, Austin, TX, US, 78746
Last Update: 18/09/2026
Austin, Texas-based Keller Williams, the world’s largest real estate franchise by agent count, has more than 1,100 offices and 176,000 agents. The franchise is also No. 1 in units and sales volume in the United States. Since 1983, the company has cultivated an agent-c...
Compliance Ranges Comparison
Swire Properties
Keller Williams Realty, LLC
Benchmark & Cyber Underwriting Signals
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for Swire Properties in 2026.
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for Keller Williams Realty, LLC in 2026.
Incident History - Swire Properties (X = Date, Y = Severity)
Swire Properties cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Keller Williams Realty, LLC (X = Date, Y = Severity)
Keller Williams Realty, LLC cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Swire Properties
Keller Williams Realty, LLC
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.