Comparison Overview
Overland Park Regional Medical Center

Overland Park Regional Medical Center
10500 Quivira Rd., Overland Park, 66213, US
Last Update: 31/03/2026
Our hospital serves the community’s healthcare needs by providing compassionate, patient and family-centered care and some of the most advanced treatment options available in the Kansas City region. Overland Park Regional Medical Center has a world-class medical staff w...

McKesson
6555 State Highway 161, Irving, Texas, US, 75039
Last Update: 02/04/2026
Welcome to the official LinkedIn page for McKesson Corporation. We're an impact-driven healthcare organization dedicated to “Advancing Health Outcomes For All.” As a global healthcare company, we touch virtually every aspect of health. Our leaders empower our people to...
Compliance Ranges Comparison

Overland Park Regional Medical Center







McKesson






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Overland Park Regional Medical Center in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for McKesson in 2026.
Incident History - Overland Park Regional Medical Center (X = Date, Y = Severity)
Overland Park Regional Medical Center cyber incidents detection timeline including parent company and subsidiaries.
Incident History - McKesson (X = Date, Y = Severity)
McKesson cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Overland Park Regional Medical Center

McKesson
FAQ
Latest Global CVEs
An authenticated user with the read role may read limited amounts of uninitialized stack memory via specially-crafted issuances of the filemd5 command
The $_internalApplyOplogUpdate aggregation pipeline stage can be used to execute a document diff containing a malformed binary diff to return memory out-of-bounds or crash the server. $_internalApplyOplogUpdate can be executed by any authenticated user with access to the aggregate command.
An authorized user could trigger a server crash by running a query with a 2dsphere index on a field that stores a GeoJSON GeometryCollection containing a Polygon with a strict-winding CRS. Strict-winding polygons are intentionally unsupported for indexing, but the guard that rejects them does not inspect members of a GeometryCollection, allowing the unsafe path to be reached which ends with an ensuing null-pointer dereference.
The ldapQueryPassword parameter, when set through the runtime setParameter command, will log the new password to the mongod.log file in plain text.
An authenticated user can cause a MongoDB server to crash or return incorrect results by creating documents that interfere with internal metadata processing during query execution. This stems from insufficient separation between user-controlled document fields and internal metadata in certain execution paths.