Comparison Overview
Baylor Scott & White Health

Baylor Scott & White Health
3500 Gaston Ave, Dallas, 75246, US
Last Update: 03/04/2026
With us by your side, there's no stopping you. It's why we're creating a new kind of healthcare at Baylor Scott & White. And we're just getting started. As the largest not-for-profit health system in the state of Texas, Baylor Scott & White promotes the health and well...

Mayo Clinic
200 First St. S.W., Rochester, Minnesota, US, 55905
Last Update: 08/06/2026
Mayo Clinic has expanded and changed in many ways, but our values remain true to the vision of our founders. Our primary value – The needs of the patient come first – guides our plans and decisions as we create the future of health care. Join us and you'll find a cultur...
Compliance Ranges Comparison

Baylor Scott & White Health







Mayo Clinic






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Baylor Scott & White Health in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Mayo Clinic has 85.19% more incidents than the average of all companies with at least one recorded incident.
Incident History - Baylor Scott & White Health (X = Date, Y = Severity)
Baylor Scott & White Health cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mayo Clinic (X = Date, Y = Severity)
Mayo Clinic cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Baylor Scott & White Health

Mayo Clinic
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.