Comparison Overview
Landmark Arabia

Landmark Arabia
Riyadh Gallery, Riyadh, 12262, SA
Last Update: 10/03/2026
Landmark Arabia is a division of Landmark Group - Middle East's leading retail and hospitality conglomerate, was launched in the Kingdom of Saudi Arabia in 1994. Since its inception, the Group and its brands have created exceptional value for communities across the regi...

H&M Group
Årstaängsvägen 13, Stockholm, Stockholm, SE, 117 75
Last Update: 05/04/2026
Founded in 1947, H&M Group is a global design company with ~4,702 stores in 76 markets and 56 online markets. At H&M Group, we believe in making great design available to everyone. It’s essential in everything we do. Our family of brands and business ventures offer cust...
Compliance Ranges Comparison

Landmark Arabia







H&M Group






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Landmark Arabia in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for H&M Group in 2026.
Incident History - Landmark Arabia (X = Date, Y = Severity)
Landmark Arabia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - H&M Group (X = Date, Y = Severity)
H&M Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Landmark Arabia

H&M Group
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.