Comparison Overview
Kanyon Yönetim İşletim ve Pazarlama A.Ş.

Kanyon Yönetim İşletim ve Pazarlama A.Ş.
Büyükdere Caddesi, Esentepe, 34394, TR
Last Update: 25/04/2026
KANYON YÖNETİM İŞLETİM VE PAZARLAMA A.Ş. Kanyon Alışveriş Merkezi’ni yönetmek üzere kurulmuş olan Kanyon Yönetim İşletim ve Pazarlama A.Ş., bu konudaki başarısının ardından ortakların diğer gayrimenkul projelerini de yönetmeye başlamıştır. Bunların arasında Eczacıbaşı’...

Toys"R"Us
Parsippany, 07054, US
Last Update: 01/04/2026
Toys“R”Us is a beloved brand known all around the world—and we know how to have fun! For over 70 years we've been the toy authority and ambassadors of all things play. Our new vision looks beyond traditional retail for a re-imagined, immersive experience for kids of all...
Compliance Ranges Comparison

Kanyon Yönetim İşletim ve Pazarlama A.Ş.







Toys"R"Us






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Kanyon Yönetim İşletim ve Pazarlama A.Ş. in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Toys"R"Us in 2026.
Incident History - Kanyon Yönetim İşletim ve Pazarlama A.Ş. (X = Date, Y = Severity)
Kanyon Yönetim İşletim ve Pazarlama A.Ş. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Toys"R"Us (X = Date, Y = Severity)
Toys"R"Us cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Kanyon Yönetim İşletim ve Pazarlama A.Ş.

Toys"R"Us
FAQ
Latest Global CVEs
A vulnerability was determined in xuxueli xxl-job up to 3.5.0. The impacted element is an unknown function of the file /jobgroup/insert. This manipulation of the argument Name causes cross site scripting. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.
A vulnerability was found in Moore Threads MTT S80 Driver Package 340.150. The affected element is the function sub_140006F0C in the library mtdispkm64.sys of the component IOCTL Handler. The manipulation results in improper privilege management. Attacking locally is a requirement. The vendor was contacted early about this disclosure but did not respond in any way.
vLLM Mooncake connector through 0.29.0 fails to properly manage GPU KV cache block ownership when concurrent child requests share a single transfer ID in prefill/decode disaggregated deployments. Attackers can trigger GPU memory exhaustion by submitting completion requests with multiple prompts, causing orphaned KV cache blocks to accumulate until process restart and eventually preventing legitimate requests from executing.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/mooncake/mooncake_connector.py#L1978-L1989
- https://github.com/vllm-project/vllm/pull/49796
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-gpu-kv-cache-leak-via-mooncake-transfer-id-collision
vLLM through 0.29.0 fails to validate the tp_size parameter in kv_transfer_params on OpenAI-compatible completion endpoints, allowing attackers to allocate unbounded memory. Attackers can supply arbitrary tp_size values in prefill/decode disaggregated deployments to exhaust memory and trigger kernel OOM-kill of the decode worker process.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/utils.py#L569-L573
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/metadata.py#L277
- https://github.com/vllm-project/vllm/pull/51137
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-unvalidated-nixl-tp-size
vLLM through 0.29.0 contains a resource exhaustion vulnerability in MooncakeConnector where rejected prefill requests create ownerless transfer placeholders that are never reclaimed. Attackers can send rejected requests to exhaust sender task pools, causing valid requests to be delayed by up to 480 seconds while health checks continue returning success.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/mooncake/mooncake_connector.py#L1234-L1242
- https://github.com/vllm-project/vllm/pull/51236
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-resource-exhaustion-via-ownerless-mooncake-transfer-placeholders