Comparison Overview

Mercy Health

VS

The Ohio State University Wexner Medical Center

Mercy Health

Cincinnati, 45237, US
Last Update: 2026-03-29
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

The Ohio State University Wexner Medical Center

410 W. 10th Ave, Columbus, OH, US, 43210
Last Update: 2026-03-23
Between 750 and 799

At The Ohio State University Wexner Medical Center you will find more than a job – you can establish a career that allows you to actually change the face of medicine. As central Ohio's only academic medical center, we emphasize learning, development and innovation in order to offer the very best in personalized care to over 1.7 million patients each year. There's plenty of opportunity for career growth too, because Ohio State's Wexner Medical Center encompasses seven hospitals, fourteen primary care offices, a walk-in clinic, two After-Hours Care locations and eleven multi-specialty clinics, as well as the College of Medicine, the School of Health and Rehabilitation Sciences, the health sciences library and the Faculty Group Practice. You'll find clinical care offered in virtually every medical specialty and subspecialty and an interdisciplinary team of healthcare experts beyond compare. Ohio State offers great pay, complete benefits, state retirement options, tuition assistance and access to the cultural and sporting resources at one of the nation’s largest universities (learn more at wexnermedical.osu.edu/careers). Outside of work, you'll discover a great quality of life. Columbus is the nation's 14th largest city with beautiful neighborhoods and a full range of activities and entertainment options. Everything we do is driven by our strategic plan, which is built on our mission to improve health in Ohio and across the world through innovation in research, education and patient care. To accomplish this, our vision calls us to push the boundaries of discovery and knowledge to solve significant problems and deliver unparalleled care. If this sounds appealing to you and you share our values of inclusiveness, determination, empathy, sincerity, ownership and innovation, Ohio State may be the perfect fit for you. Apply today and let's see what we can do together to change the world through medicine.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

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
https://images.rankiteo.com/companyimages/the-ohio-state-university-wexner-medical-center.jpeg
The Ohio State University Wexner 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
Compliance Summary
Mercy Health
100%
Compliance Rate
0/4 Standards Verified
The Ohio State University Wexner Medical Center
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 Mercy Health in 2026.

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

No incidents recorded for The Ohio State University Wexner Medical Center in 2026.

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

Mercy Health cyber incidents detection timeline including parent company and subsidiaries

Incident History — The Ohio State University Wexner Medical Center (X = Date, Y = Severity)

The Ohio State University Wexner Medical Center cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

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
https://images.rankiteo.com/companyimages/the-ohio-state-university-wexner-medical-center.jpeg
The Ohio State University Wexner Medical Center
Incidents

No Incident

FAQ

The Ohio State University Wexner 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 The Ohio State University Wexner Medical Center company has not reported any.

In the current year, The Ohio State University Wexner Medical Center company and Mercy Health company have not reported any cyber incidents.

Neither The Ohio State University Wexner Medical Center company nor Mercy Health company has reported experiencing a ransomware attack publicly.

Mercy Health company has disclosed at least one data breach, while the other The Ohio State University Wexner Medical Center company has not reported such incidents publicly.

Neither The Ohio State University Wexner Medical Center company nor Mercy Health company has reported experiencing targeted cyberattacks publicly.

Neither Mercy Health company nor The Ohio State University Wexner Medical Center company has reported experiencing or disclosing vulnerabilities publicly.

Neither Mercy Health nor The Ohio State University Wexner Medical Center holds any compliance certifications.

Neither company holds any compliance certifications.

Mercy Health company has more subsidiaries worldwide compared to The Ohio State University Wexner Medical Center company.

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

Neither Mercy Health nor The Ohio State University Wexner Medical Center holds SOC 2 Type 1 certification.

Neither Mercy Health nor The Ohio State University Wexner Medical Center holds SOC 2 Type 2 certification.

Neither Mercy Health nor The Ohio State University Wexner Medical Center holds ISO 27001 certification.

Neither Mercy Health nor The Ohio State University Wexner Medical Center holds PCI DSS certification.

Neither Mercy Health nor The Ohio State University Wexner Medical Center holds HIPAA certification.

Neither Mercy Health nor The Ohio State University Wexner Medical Center holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

A vulnerability was identified in Totolink A3300R 17.0.0cu.557_b20221024. This affects the function setLanCfg of the file /cgi-bin/cstecgi.cgi of the component Parameter Handler. The manipulation of the argument lanIp leads to command injection. Remote exploitation of the attack is possible. The exploit is publicly available and might be used.

Risk Information
cvss2
Base: 6.5
Severity: LOW
AV:N/AC:L/Au:S/C:P/I:P/A:P
cvss3
Base: 6.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/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
Description

Perl versions from 5.9.4 before 5.40.4-RC1, from 5.41.0 before 5.42.2-RC1, from 5.43.0 before 5.43.9 contain a vulnerable version of Compress::Raw::Zlib. Compress::Raw::Zlib is included in the Perl package as a dual-life core module, and is vulnerable to CVE-2026-3381 due to a vendored version of zlib which has several vulnerabilities, including CVE-2026-27171. The bundled Compress::Raw::Zlib was updated to version 2.221 in Perl blead commit c75ae9cc164205e1b6d6dbd57bd2c65c8593fe94.

Description

Ghidra versions prior to 12.0.3 improperly process annotation directives embedded in automatically extracted binary data, resulting in arbitrary command execution when an analyst interacts with the UI. Specifically, the @execute annotation (which is intended for trusted, user-authored comments) is also parsed in comments generated during auto-analysis (such as CFStrings in Mach-O binaries). This allows a crafted binary to present seemingly benign clickable text which, when clicked, executes attacker-controlled commands on the analyst’s machine.

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

A critical security vulnerability in parisneo/lollms versions up to 2.2.0 allows any authenticated user to accept or reject friend requests belonging to other users. The `respond_request()` function in `backend/routers/friends.py` does not implement proper authorization checks, enabling Insecure Direct Object Reference (IDOR) attacks. Specifically, the `/api/friends/requests/{friendship_id}` endpoint fails to verify whether the authenticated user is part of the friendship or the intended recipient of the request. This vulnerability can lead to unauthorized access, privacy violations, and potential social engineering attacks. The issue has been addressed in version 2.2.0.

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

A Server-Side Request Forgery (SSRF) vulnerability exists in parisneo/lollms versions prior to 2.2.0, specifically in the `/api/files/export-content` endpoint. The `_download_image_to_temp()` function in `backend/routers/files.py` fails to validate user-controlled URLs, allowing attackers to make arbitrary HTTP requests to internal services and cloud metadata endpoints. This vulnerability can lead to internal network access, cloud metadata access, information disclosure, port scanning, and potentially remote code execution.

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