Comparison Overview
LEO Pharma Canada

LEO Pharma Canada
Toronto, CA
Last Update: 09/06/2026
LEO Pharma helps people achieve healthy skin. We offer care solutions to patients in more than 100 countries globally. This is the Canadian affiliate page for LEO Pharma.

EMS
Rodovia Jorn. Francisco Aguirre Proenca, Hortolandia, 13186-525, BR
Last Update: 01/04/2026
Fundada há mais de 60 anos e com capital 100% nacional, a EMS é a líder do mercado farmacêutico brasileiro há 19 anos consecutivos, pertencente ao Grupo NC, um dos maiores conglomerados brasileiros. A empresa ocupa também a liderança no segmento de genéricos desde 2013...
Compliance Ranges Comparison

LEO Pharma Canada







EMS






Benchmark & Cyber Underwriting Signals
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for LEO Pharma Canada in 2026.
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for EMS in 2026.
Incident History - LEO Pharma Canada (X = Date, Y = Severity)
LEO Pharma Canada cyber incidents detection timeline including parent company and subsidiaries.
Incident History - EMS (X = Date, Y = Severity)
EMS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

LEO Pharma Canada

EMS
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.