Comparison Overview
Evans Hotels
Evans Hotels
3999 Mission Boulevard, None, San Diego, California, US, 92109
Last Update: 31/03/2026
Evans Hotels is the premier provider of resort accommodations in one of San Diego’s most beautiful and scenic locations, Mission Bay Park. Since 1953, it has been our mission to match the superior natural beauty of this landscape with a superior level of service, in ad...
Wyndham Hotels & Resorts
22 Sylvan Way, Parsippany, 07054, US
Last Update: 11/09/2026
We are Wyndham Hotels & Resorts. We are the world’s largest hotel franchising company by the number of franchised properties, with approximately 8,300 hotels across approximately 100 countries on six continents. We operate a portfolio of 25 hotel brands: Whether choosi...
Compliance Ranges Comparison
Evans Hotels
Wyndham Hotels & Resorts
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Evans Hotels in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Wyndham Hotels & Resorts in 2026.
Incident History - Evans Hotels (X = Date, Y = Severity)
Evans Hotels cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Wyndham Hotels & Resorts (X = Date, Y = Severity)
Wyndham Hotels & Resorts cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Evans Hotels
Wyndham Hotels & Resorts
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.