Comparison Overview
Envoyage CA
Envoyage CA
35 McCaul St 7th Floor, Toronto, Ontario, M5T 1V7, CA
Last Update: 05/12/2025
The Envoyage independent community spans five countries and includes specialist groups for luxury and corporate agencies. Part of Flight Centre Travel Group, Envoyage empowers independent travel agencies and entrepreneurial advisors to benefit from the buying power, exp...
Europcar Mobility Group
13 ter Boulevard Berthier, Paris, Île-de-France, FR, 75017
Last Update: 08/09/2026
Europcar Mobility Group is a global mobility player, with 75 years of mobility services expertise and a leading position in Europe. “We help to change the way you move” is what we stand for and brings us together. More than ever, we're committed to delivering simple, s...
Compliance Ranges Comparison
Envoyage CA
Europcar Mobility Group
Benchmark & Cyber Underwriting Signals
Incidents vs Travel Arrangements Industry Avg (This Year)
No incidents recorded for Envoyage CA in 2026.
Incidents vs Travel Arrangements Industry Avg (This Year)
No incidents recorded for Europcar Mobility Group in 2026.
Incident History - Envoyage CA (X = Date, Y = Severity)
Envoyage CA cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Europcar Mobility Group (X = Date, Y = Severity)
Europcar Mobility Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Envoyage CA
Europcar Mobility Group
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.