Comparison Overview
Sharp

Sharp
匠町1 堺市堺区, 大阪府 590-8522, JP
Last Update: 23/03/2026
„ÄêCorporate Name„Äë Sharp Corporation „ÄêHead Office„Äë 1 Takumi-cho, Sakai-ku, Sakai City, Osaka 590-8522, Japan „ÄêManagement Representatives„Äë Masahiro Okitsu, President & Chief Executive Officer „ÄêBusiness Activities„Äë Mainly manufacturing and sales of teleco...

Samsung Mobile
DongSuwon P.O.BOX 105, 416, Maetan-3dong, Gyeonggi-do, 443-742, KR
Last Update: 01/04/2026
Samsung Mobile is at the forefront of mobile intelligence, shaping the future with Galaxy AI. With the next evolution of Galaxy AI, we are making lives simpler–reducing stress, creating more time, and getting the help you need without even having to ask. In this era of...
Compliance Ranges Comparison

Sharp







Samsung Mobile






Benchmark & Cyber Underwriting Signals
Incidents vs Consumer Electronics Industry Avg (This Year)
No incidents recorded for Sharp in 2026.
Incidents vs Consumer Electronics Industry Avg (This Year)
No incidents recorded for Samsung Mobile in 2026.
Incident History - Sharp (X = Date, Y = Severity)
Sharp cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Samsung Mobile (X = Date, Y = Severity)
Samsung Mobile cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Sharp

Samsung Mobile
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.