Comparison Overview
ILTM

ILTM
undefined, Richmond, undefined, undefined, GB
Last Update: 27/11/2025
ILTM is a collection of global, local and specialist luxury travel events. Each event introduces an unrivalled selection of luxury travel brands to ILTM’s extensive network of hand-picked luxury travel advisors, through bespoke appointment programmes and networking se...

Encore
5100 N River Rd, Schiller Park, 60176, US
Last Update: 14/09/2026
Encore is your full-service event production partner with more than 80 years of experience. Each year, Encore delivers more than 350,000 events in 20 countries across North America, Europe, the Middle East, Australia and Asia Pacific. Through event technology, rigging...
Compliance Ranges Comparison

ILTM







Encore






Benchmark & Cyber Underwriting Signals
Incidents vs Events Services Industry Avg (This Year)
No incidents recorded for ILTM in 2026.
Incidents vs Events Services Industry Avg (This Year)
No incidents recorded for Encore in 2026.
Incident History - ILTM (X = Date, Y = Severity)
ILTM cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Encore (X = Date, Y = Severity)
Encore cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

ILTM

Encore
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.