Comparison Overview
(주)GS리테일(GS Retail Inc.)

(주)GS리테일(GS Retail Inc.)
GS Tower 508, Nonhyeon-ro, Gangnam-gu, Seoul, KR, 06141
Last Update: 31/08/2026
GS리테일은 최고의 제품과 진실된 서비스로 고객을 만족시키며 높은 수익을 창출하고, 지속적으로 성장하는 기업입니다. 유통업계의 Leading Company인 GS리테일은 편의점, 수퍼, 헬스&뷰티, 호텔 사업 등 다양한 사업을 기반으로 트렌드를 선도하고 있습니다. 탁월한 조직 역량과 경영을 바탕으로 GS리테일은 꾸준히 성장과 이익의 균형이 잡힌 성과를 내고 있습니다. 통합 쇼핑 플랫폼의 선두 주자인 GS홈쇼핑은 GS리테일의 가족이 되었습니다. GS홈쇼핑은 TV, 카탈로그, 인터...

Sobeys
115 King Street, Stellarton, Nova Scotia, CA, B0K 1S0
Last Update: 14/09/2026
As one of only two national grocery retailers in Canada, Sobeys Inc. serves the food shopping needs of Canadians with more than 1,500 stores in 10 provinces with retail banners that include Sobeys, Safeway, IGA, Foodland, FreshCo, Price Chopper, Thrifty Foods and Lawton...
Compliance Ranges Comparison

(주)GS리테일(GS Retail Inc.)







Sobeys






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
(주)GS리테일(GS Retail Inc.) has 44.44% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Sobeys in 2026.
Incident History - (주)GS리테일(GS Retail Inc.) (X = Date, Y = Severity)
(주)GS리테일(GS Retail Inc.) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sobeys (X = Date, Y = Severity)
Sobeys cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

(주)GS리테일(GS Retail Inc.)

Sobeys
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