Comparison Overview
Willow Brook Rehabilitation & Healthcare Center

Willow Brook Rehabilitation & Healthcare Center
90 West St, Wilmington, 01887, US
Last Update: 23/03/2026
Willow Brook Rehabilitation & Healthcare Center is proud to introduce the next generation of post acute care to Wilmington, MA communities. Our skilled nursing and transitional care center offers an inviting atmosphere where every patient is made to feel comfortable. W...

Mercy
15740 South Outer Forty Road, Chesterfield, 63017 , US
Last Update: 29/03/2026
Mercy, one of the 15 largest U.S. health systems and named the top large system in the U.S. for excellent patient experience by NRC Health, serves millions annually with nationally recognized care and one of the nation’s largest and highest performing Accountable Care O...
Compliance Ranges Comparison

Willow Brook Rehabilitation & Healthcare Center







Mercy






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

Willow Brook Rehabilitation & Healthcare Center

Mercy
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.