Comparison Overview
Wrigley

Wrigley
1132 W Blackhawk St, Chicago, Illinois, undefined, US
Last Update: 08/12/2025
We’ve moved! Please visit Mars Wrigley Confectionery’s Showcase Page for job opportunities and company updates. *** Page subject to mars.com/legal. Mars, Inc. is not responsible for any content or activity made available via third party sites or services.

Arçelik Türkiye
Karaağaç Caddesi, İstanbul, 34445, TR
Last Update: 02/04/2026
Arçelik Türkiye olarak, "Dünyaya Saygılı Dünyada Saygın" misyonuyla yola çıkıyoruz ve teknoloji, insan kaynağı ve üretim gücümüzü sürdürülebilir bir gelecek için kullanıyoruz. 1955 yılında başlayan yolculuğumuz bugün, 22 marka, 46 üretim tesisi, 55.000 çalışan ve 58 ül...
Compliance Ranges Comparison

Wrigley







Arçelik Türkiye






Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Wrigley in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Arçelik Türkiye in 2026.
Incident History - Wrigley (X = Date, Y = Severity)
Wrigley cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Arçelik Türkiye (X = Date, Y = Severity)
Arçelik Türkiye cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Wrigley

Arçelik Türkiye
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.