Comparison Overview
BDO Hungary
BDO Hungary
Kőér utca 2/a, Budapest, undefined, 1103, HU
Last Update: 01/02/2026
BDO is the brand name for the BDO network and for each of our BDO Member Firms. Our brand stands for exceptional client service, delivered by exceptional people. BDO's global network provides advisory services in 164 countries, with over 95,000 people working out of m...
Dubai Holding
Umm Suqeim Road, across from Madinat Jumeirah, Dubai, 66000 , AE
Last Update: 08/09/2026
Dubai Holding is a diversified global investment company that continues to power Dubai’s growth across 10 key sectors, including real estate, hospitality, leisure & entertainment, media, ICT, design, education, retail, manufacturing & logistics and science. Since 2004...
Compliance Ranges Comparison
BDO Hungary
Dubai Holding
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for BDO Hungary in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Dubai Holding in 2026.
Incident History - BDO Hungary (X = Date, Y = Severity)
BDO Hungary cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Dubai Holding (X = Date, Y = Severity)
Dubai Holding cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
BDO Hungary
Dubai Holding
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.