Comparison Overview

Merck

VS

AbbVie

Merck

126 E Lincoln Ave, P.O. Box 2000, Rahway, New Jersey, US, 07065
Last Update: 2025-12-09
View Profile
Between 800 and 849
http://merck.us/2J2xAUh

At Merck, known as MSD outside of the United States and Canada, we are unified around our purpose: We use the power of leading-edge science to save and improve lives around the world. For more than 130 years, we have brought hope to humanity through the development of important medicines and vaccines. We aspire to be the premier research-intensive biopharmaceutical company in the world – and today, we are at the forefront of research to deliver innovative health solutions that advance the prevention and treatment of diseases in people and animals. We foster a diverse and inclusive global workforce and operate responsibly every day to enable a safe, sustainable and healthy future for all people and communities. For more information, visit www.merck.com. This site is intended for residents of the United States and Canada and their territories only. FLS: http://merck.us/3TKXNuZ

NAICS: 3254
NAICS Definition: Pharmaceutical and Medicine Manufacturing
Employees: 42,297
Subsidiaries: 2
12-month incidents
1
Known data breaches
1
Attack type number
2
View Profile

AbbVie

1 Waukegan Road, None, North Chicago, Illinois, US, 60064
Last Update: 2025-12-11
Between 800 and 849
http://www.abbvie.com

AbbVie is a global biopharmaceutical company focused on creating medicines and solutions that put impact first — for patients, communities, and our world. We aim to address complex health issues and enhance people's lives through our core therapeutic areas: immunology, oncology, neuroscience, eye care, aesthetics and other areas of unmet need. Learn more about us at www.abbvie.com and review our community guidelines at https://www.abbvie.com/social-media-community-guidelines.html.

NAICS: 3254
NAICS Definition: Pharmaceutical and Medicine Manufacturing
Employees: 58,020
Subsidiaries: 15
12-month incidents
0
Known data breaches
1
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/merck.jpeg
Merck
—
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/abbvie.jpeg
AbbVie
—
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
Merck
100%
Compliance Rate
0/4 Standards Verified
AbbVie
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

Merck has 25.0% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for AbbVie in 2025.

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

Merck cyber incidents detection timeline including parent company and subsidiaries

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

AbbVie cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/merck.jpeg
Merck
Incidents

Date Detected: 9/2025
Type:Breach
Blog: Blog

Date Detected: 06/2017
Type:Cyber Attack
Blog: Blog
https://images.rankiteo.com/companyimages/abbvie.jpeg
AbbVie
Incidents

Date Detected: 6/2023
Type:Breach
Attack Vector: Exploitation of Vulnerability
Motivation: Financial gain
Blog: Blog

FAQ

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

Merck company has faced a higher number of disclosed cyber incidents historically compared to AbbVie company.

In the current year, Merck company has reported more cyber incidents than AbbVie company.

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

Both AbbVie company and Merck company have disclosed experiencing at least one data breach.

Merck company has reported targeted cyberattacks, while AbbVie company has not reported such incidents publicly.

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

Neither Merck nor AbbVie holds any compliance certifications.

Neither company holds any compliance certifications.

AbbVie company has more subsidiaries worldwide compared to Merck company.

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

Neither Merck nor AbbVie holds SOC 2 Type 1 certification.

Neither Merck nor AbbVie holds SOC 2 Type 2 certification.

Neither Merck nor AbbVie holds ISO 27001 certification.

Neither Merck nor AbbVie holds PCI DSS certification.

Neither Merck nor AbbVie holds HIPAA certification.

Neither Merck nor AbbVie holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss3
Base: 8.1
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
References
Description

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss3
Base: 2.9
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
References
Description

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/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
References
Description

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss3
Base: 4.5
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:L
References
Description

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N
References