Comparison Overview
Magnum AS

Magnum AS
Vae, Laagri, 76401, EE
Last Update: 02/04/2026
Magnum AS, founded in 1992, is a subsidiary of a privately owned Estonian investment company MM Grupp and its headquarters is located in Tallinn. Companies under the Magnum AS group mostly operate in the retail and wholesale sector and have innovative up-to-date logisti...

Fresenius Kabi
Else-Kröner-Straße 1, Bad Homburg, Hessen, DE, 61352
Last Update: 01/04/2026
As a global healthcare company, Fresenius Kabi is Committed to Life. The company’s products, technologies, and services are used for the therapy and care of critically and chronically ill patients. With over 41,000 employees and present in over 100 countries, Fresenius ...
Compliance Ranges Comparison

Magnum AS







Fresenius Kabi






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

Magnum AS

Fresenius Kabi
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.