Comparison Overview

Vanderbilt University Medical Center

VS

Mercy Health

Vanderbilt University Medical Center

2525 West End Ave., Ste. 500, Nashville, 37203, US
Last Update: 2026-01-17

From specializing in transplants and pediatric cancer to solving undiagnosed diseases, we know solving the most complex problems prepares us to solve any problem. We are committed to excellence in patient care, research, and medical education and training. We thrive on challenges, embrace collaboration and champion innovation. We are a growing academic health system with seven hospitals and hundreds of clinics throughout the Mid-South, as well as one of the nation's top biomedical research programs. Join us: https://www.vumc.org/careers/ We are regularly ranked among the nation's leading hospitals in terms of quality and effectiveness. Our tireless pursuit of personalized care has earned scores of patient satisfaction awards. Our research is expanding the frontiers of medical knowledge, and every day we advance toward a better understanding of human health. We blend new discoveries and technology into health education, preparing distinguished medical professionals to offer the most advanced and compassionate care possible. We set the pace for health care in the Southeast, and we are a nationally respected referral center. We are building on nearly 150 years of accomplishments to shape the future of health care the world over. For information about our clinical services for adults throughout the Vanderbilt Health system, visit http://www.VanderbiltHealth.com. For information about our comprehensive Monroe Carell Jr. Children's Hospital at Vanderbilt, visit https://childrenshospitalvanderbilt.org/ Social Media Participation Guidelines: http://tinyurl.com/vumcpolicy

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 20,987
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0

Mercy Health

Cincinnati, 45237, US
Last Update: 2026-01-18
Between 750 and 799

At Mercy Health, we understand that every family is a universe. A network of people who love, and support, and count on one other to be there. Everybody means the world to someone and we are committed to care for others so they can be there for the ones they love. With nearly 35,000 employees across regions of Ohio and Kentucky, we’re one of the largest health care systems in the country. At each of our more than 600 points of care, we deliver high-quality, compassionate care with one united purpose: to help our patients be well in mind, body and spirit.

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 14,071
Subsidiaries: 4
12-month incidents
0
Known data breaches
3
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/vanderbilt-university-medical-center.jpeg
Vanderbilt University Medical Center
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/mercyhealth-chp.jpeg
Mercy Health
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
Vanderbilt University Medical Center
100%
Compliance Rate
0/4 Standards Verified
Mercy Health
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Hospitals and Health Care Industry Average (This Year)

No incidents recorded for Vanderbilt University Medical Center in 2026.

Incidents vs Hospitals and Health Care Industry Average (This Year)

No incidents recorded for Mercy Health in 2026.

Incident History — Vanderbilt University Medical Center (X = Date, Y = Severity)

Vanderbilt University Medical Center cyber incidents detection timeline including parent company and subsidiaries

Incident History — Mercy Health (X = Date, Y = Severity)

Mercy Health cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/vanderbilt-university-medical-center.jpeg
Vanderbilt University Medical Center
Incidents

No Incident

https://images.rankiteo.com/companyimages/mercyhealth-chp.jpeg
Mercy Health
Incidents

Date Detected: 01/2020
Type:Breach
Attack Vector: Invoice Printing Error
Blog: Blog

Date Detected: 08/2016
Type:Breach
Blog: Blog

Date Detected: 4/2016
Type:Breach
Attack Vector: Inadvertent Exposure (Misconfigured Internet-Accessible Files)
Blog: Blog

FAQ

Vanderbilt University Medical Center company demonstrates a stronger AI Cybersecurity Score compared to Mercy Health company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Mercy Health company has historically faced a number of disclosed cyber incidents, whereas Vanderbilt University Medical Center company has not reported any.

In the current year, Mercy Health company and Vanderbilt University Medical Center company have not reported any cyber incidents.

Neither Mercy Health company nor Vanderbilt University Medical Center company has reported experiencing a ransomware attack publicly.

Mercy Health company has disclosed at least one data breach, while Vanderbilt University Medical Center company has not reported such incidents publicly.

Neither Mercy Health company nor Vanderbilt University Medical Center company has reported experiencing targeted cyberattacks publicly.

Neither Vanderbilt University Medical Center company nor Mercy Health company has reported experiencing or disclosing vulnerabilities publicly.

Neither Vanderbilt University Medical Center nor Mercy Health holds any compliance certifications.

Neither company holds any compliance certifications.

Mercy Health company has more subsidiaries worldwide compared to Vanderbilt University Medical Center company.

Vanderbilt University Medical Center company employs more people globally than Mercy Health company, reflecting its scale as a Hospitals and Health Care.

Neither Vanderbilt University Medical Center nor Mercy Health holds SOC 2 Type 1 certification.

Neither Vanderbilt University Medical Center nor Mercy Health holds SOC 2 Type 2 certification.

Neither Vanderbilt University Medical Center nor Mercy Health holds ISO 27001 certification.

Neither Vanderbilt University Medical Center nor Mercy Health holds PCI DSS certification.

Neither Vanderbilt University Medical Center nor Mercy Health holds HIPAA certification.

Neither Vanderbilt University Medical Center nor Mercy Health holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

SummaryA command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. Root causeThe commitHash variable, derived from user input via the --commit-hash CLI argument, is interpolated directly into a shell command using template literals (e.g.,  execSync(`git show -s --format=%B ${commitHash}`)). Shell metacharacters are interpreted by the shell, enabling command execution. ImpactThis vulnerability is generally hard to exploit, as it requires --commit-hash to be attacker controlled. The vulnerability primarily affects CI/CD environments where `wrangler pages deploy` is used in automated pipelines and the --commit-hash parameter is populated from external, potentially untrusted sources. An attacker could exploit this to: * Run any shell command. * Exfiltrate environment variables. * Compromise the CI runner to install backdoors or modify build artifacts. Credits Disclosed responsibly by kny4hacker. Mitigation * Wrangler v4 users are requested to upgrade to Wrangler v4.59.1 or higher. * Wrangler v3 users are requested to upgrade to Wrangler v3.114.17 or higher. * Users on Wrangler v2 (EOL) should upgrade to a supported major version.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N/E:X/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

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

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

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle VM VirtualBox accessible data as well as unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L).

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

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

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

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

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