Comparison Overview

Takeda

VS

Merck Group

Takeda

Tokyo, JP
Last Update: 2026-01-18
Between 800 and 849

We strive to transform lives. While the science we advance is constantly evolving, our core purpose is enduring. For more than two centuries, our values have guided us to do what’s right for patients and for society. We know that changing lives requires us to do things differently. We start by listening to and addressing what really matters to patients, the people who love them, and those in the healthcare system who provide care. And that’s what inspires us all to be bold, push boundaries and set new standards that open up greater opportunities. Read our community guidelines: https://takeda.info/communityguidelines

NAICS: 3254
NAICS Definition: Pharmaceutical and Medicine Manufacturing
Employees: 37,228
Subsidiaries: 6
12-month incidents
0
Known data breaches
1
Attack type number
1

Merck Group

Frankfurter Str. 250, Darmstadt, DE, 64293
Last Update: 2026-01-18
Between 800 and 849

This channel is not intended for U.S. and Canadian visitors. Merck operates in the U.S. and Canada as EMD Serono in Healthcare, MilliporeSigma in Life Science and EMD Electronics in Electronics. An unaffiliated and unrelated company, Merck & Co., Inc., Kenilworth, NJ, US holds the rights in the trademark MERCK in the U.S. and Canada. _______________________________ We are Merck, a leading global science and technology company headquartered in Germany. We are curious explorers, courageous pioneers, and ingenious inventors. Our colleagues across the globe love innovating with science and technology to enrich people’s lives with our solutions in Life Science, Healthcare, and Electronics. Together, we dream big and are passionate about caring for our rich mix of people, customers, patients, and the planet. We believe in the positive power of science and technology. It has determined our actions since 1668 and inspires us to continue researching for a future worth living. As a family-owned company with over 350 years of experience, we stand for sustainability, responsibility, and innovative strength. We take pride in being a diverse and inclusive company that values and fosters the talents and abilities of our employees. That's why we are always looking for curious minds that see themselves imagining the unimaginable with us. Work your Magic and join Merck. Legal Disclaimer: www.merckgroup.com/en/legal-disclaimer.html Data Privacy Declaration: www.merckgroup.com/en/privacy-statement

NAICS: 3254
NAICS Definition: Pharmaceutical and Medicine Manufacturing
Employees: 32,268
Subsidiaries: 3
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/takeda-pharmaceuticals.jpeg
Takeda
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/merck-group.jpeg
Merck Group
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Takeda
100%
Compliance Rate
0/4 Standards Verified
Merck Group
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for Takeda in 2026.

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for Merck Group in 2026.

Incident History — Takeda (X = Date, Y = Severity)

Takeda cyber incidents detection timeline including parent company and subsidiaries

Incident History — Merck Group (X = Date, Y = Severity)

Merck Group cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/takeda-pharmaceuticals.jpeg
Takeda
Incidents

Date Detected: 1/2024
Type:Breach
Attack Vector: Credential Stuffing
Blog: Blog
https://images.rankiteo.com/companyimages/merck-group.jpeg
Merck Group
Incidents

No Incident

FAQ

Takeda company demonstrates a stronger AI Cybersecurity Score compared to Merck Group company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Takeda company has historically faced a number of disclosed cyber incidents, whereas Merck Group company has not reported any.

In the current year, Merck Group company and Takeda company have not reported any cyber incidents.

Neither Merck Group company nor Takeda company has reported experiencing a ransomware attack publicly.

Takeda company has disclosed at least one data breach, while the other Merck Group company has not reported such incidents publicly.

Neither Merck Group company nor Takeda company has reported experiencing targeted cyberattacks publicly.

Neither Takeda company nor Merck Group company has reported experiencing or disclosing vulnerabilities publicly.

Neither Takeda nor Merck Group holds any compliance certifications.

Neither company holds any compliance certifications.

Takeda company has more subsidiaries worldwide compared to Merck Group company.

Takeda company employs more people globally than Merck Group company, reflecting its scale as a Pharmaceutical Manufacturing.

Neither Takeda nor Merck Group holds SOC 2 Type 1 certification.

Neither Takeda nor Merck Group holds SOC 2 Type 2 certification.

Neither Takeda nor Merck Group holds ISO 27001 certification.

Neither Takeda nor Merck Group holds PCI DSS certification.

Neither Takeda nor Merck Group holds HIPAA certification.

Neither Takeda nor Merck Group holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Improper validation of specified type of input in M365 Copilot allows an unauthorized attacker to disclose information over a network.

Risk Information
cvss3
Base: 9.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
Description

Improper access control in Azure Front Door (AFD) allows an unauthorized attacker to elevate privileges over a network.

Risk Information
cvss3
Base: 9.8
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Description

Azure Entra ID Elevation of Privilege Vulnerability

Risk Information
cvss3
Base: 9.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
Description

Moonraker is a Python web server providing API access to Klipper 3D printing firmware. In versions 0.9.3 and below, instances configured with the "ldap" component enabled are vulnerable to LDAP search filter injection techniques via the login endpoint. The 401 error response message can be used to determine whether or not a search was successful, allowing for brute force methods to discover LDAP entries on the server such as user IDs and user attributes. This issue has been fixed in version 0.10.0.

Risk Information
cvss4
Base: 2.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Runtipi is a Docker-based, personal homeserver orchestrator that facilitates multiple services on a single server. Versions 3.7.0 and above allow an authenticated user to execute arbitrary system commands on the host server by injecting shell metacharacters into backup filenames. The BackupManager fails to sanitize the filenames of uploaded backups. The system persists user-uploaded files directly to the host filesystem using the raw originalname provided in the request. This allows an attacker to stage a file containing shell metacharacters (e.g., $(id).tar.gz) at a predictable path, which is later referenced during the restore process. The successful storage of the file is what allows the subsequent restore command to reference and execute it. This issue has been fixed in version 4.7.0.

Risk Information
cvss3
Base: 8.0
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H