Comparison Overview
Jabra Hearing

Jabra Hearing
8001 E Bloomington Fwy, Bloomington, Minnesota, 55420, US
Last Update: 27/10/2025
We’re on a mission to empower tens of millions of people to hear better through convenient, personalized hearing care — at a fraction of the cost thanks to telemedicine. In three years, we went from a scrappy startup to a leader in the direct-to-consumer hearing care sp...

El Corte Inglés
Hermosilla, 112, Madrid, 28009, ES
Last Update: 01/04/2026
El Corte Inglés is a world leader in large department stores and a benchmark of Spanish distribution. With more than 70 years' experience, the Group has maintained from the outset a policy of customer service and an ongoing concern with adapting itself to suit the ...
Compliance Ranges Comparison

Jabra Hearing







El Corte Inglés






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Jabra Hearing in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for El Corte Inglés in 2026.
Incident History - Jabra Hearing (X = Date, Y = Severity)
Jabra Hearing cyber incidents detection timeline including parent company and subsidiaries.
Incident History - El Corte Inglés (X = Date, Y = Severity)
El Corte Inglés cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Jabra Hearing

El Corte Inglés
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.