Comparison Overview
Tmall

Tmall
969 West Wen Yi Road, Hangzhou, 311121, CN
Last Update: 19/06/2026
Launched in April 2008, Tmall.com (www.tmall.com) is dedicated to providing a premium shopping experience for increasingly sophisticated Chinese consumers in search of top-quality branded merchandise. A large number of international and Chinese brands and retailers have...

Cimpress
Xerox Technology Park, Dundalk, A91 H9N9, IE
Last Update: 07/09/2026
Cimpress plc (Nasdaq: CMPR) invests in and builds customer-focused, entrepreneurial, mass-customization businesses for the long term. Mass customization is a competitive strategy which seeks to produce goods and services to meet individual customer needs with near mass ...
Compliance Ranges Comparison

Tmall







Cimpress






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

Tmall

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