Comparison Overview
MSD Ukraine

MSD Ukraine
Николая Амосова , Киев, Киевская, 03038, UA
Last Update: 10/03/2026
MSD is a leading global biopharmaceutical company that has been inventing for life for more than a century. Bringing forward medicines and vaccines for many of the world's most challenging diseases. Through our prescription medicines, vaccines, biologic therapies, and a...

Novartis
Novartis Campus, Basel, 4002, CH
Last Update: 04/08/2026
Novartis is an innovative medicines company. Every day, working to reimagine medicine to improve and extend people’s lives so that patients, healthcare professionals and societies are empowered in the face of serious disease. Our medicines reach more than 250 million pe...
Compliance Ranges Comparison

MSD Ukraine







Novartis






Benchmark & Cyber Underwriting Signals
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for MSD Ukraine in 2026.
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
Novartis has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - MSD Ukraine (X = Date, Y = Severity)
MSD Ukraine cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Novartis (X = Date, Y = Severity)
Novartis cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

MSD Ukraine

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