Comparison Overview
BDO Esnad
BDO Esnad
68 El Marghany street, Heliopolis, Cairo, 11471, EG
Last Update: 12/03/2026
BDO Esnad- Egyptian Joint Stock Company and a member of BDO International Limited- is a leading Business Process Service Provider providing organizations with BPO services that aim to drive long-term cost reductions while keeping a focus on continuous performance improv...
Majorel
Luxembourg, LU
Last Update: 01/04/2026
Majorel has been acquired by TP allowing us to deliver even more exceptional services in more locations worldwide and on a greater scale than ever before. We deliver the most advanced, digitally-powered business services to help the world’s best brands streamline their...
Compliance Ranges Comparison
BDO Esnad
Majorel
Benchmark & Cyber Underwriting Signals
Incidents vs Outsourcing and Offshoring Consulting Industry Avg (This Year)
No incidents recorded for BDO Esnad in 2026.
Incidents vs Outsourcing and Offshoring Consulting Industry Avg (This Year)
Majorel has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - BDO Esnad (X = Date, Y = Severity)
BDO Esnad cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Majorel (X = Date, Y = Severity)
Majorel cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
BDO Esnad
Majorel
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.