Comparison Overview
Bitdefender CZ & SK

Bitdefender CZ & SK
Jordánská 391, Praha, 198 00, CZ
Last Update: 27/02/2026
Společnost Bitdefender je lídrem v oblasti kybernetické bezpečnosti, který poskytuje nejlepší řešení prevence, detekce a reakce na hrozby ve své třídě po celém světě. Bitdefender střeží miliony spotřebitelů, firem a státních úřadů a organizací, a je důvěryhodným odborn...

Alibaba.com
699 Wang Shang Road, Hangzhou, 310052, CN
Last Update: 08/09/2026
The first business of Alibaba Group, Alibaba.com (www.alibaba.com) is the leading platform for global wholesale trade serving millions of buyers and suppliers around the world. Through Alibaba.com, small businesses can sell their products to companies in other countries...
Compliance Ranges Comparison

Bitdefender CZ & SK







Alibaba.com






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Bitdefender CZ & SK in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Alibaba.com in 2026.
Incident History - Bitdefender CZ & SK (X = Date, Y = Severity)
Bitdefender CZ & SK cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Alibaba.com (X = Date, Y = Severity)
Alibaba.com cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Bitdefender CZ & SK

Alibaba.com
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.