Comparison Overview
Xenios AG - a Fresenius Medical Care company

Xenios AG - a Fresenius Medical Care company
Im Zukunftspark 1, Heilbronn, Baden-Württemberg, DE, 74076
Last Update: 11/02/2026
At Xenios, a Fresenius Medical Care company, we offer ECMO treatments for patients suffering from cardiac and/or pulmonary failure. Based on a holistic understanding of human physiology, we develop intelligent technological solutions that can be vital for the survival o...

Danaher Corporation
2200 Pennsylvania Ave NW, Washington, 20037, US
Last Update: 04/04/2026
Danaher is a leading global life sciences and diagnostics innovator, committed to accelerating the power of science and technology to improve human health. We partner with customers across the globe to help them solve their most complex challenges, architecting solution...
Compliance Ranges Comparison

Xenios AG - a Fresenius Medical Care company







Danaher Corporation






Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Xenios AG - a Fresenius Medical Care company in 2026.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Danaher Corporation in 2026.
Incident History - Xenios AG - a Fresenius Medical Care company (X = Date, Y = Severity)
Xenios AG - a Fresenius Medical Care company cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Danaher Corporation (X = Date, Y = Severity)
Danaher Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Xenios AG - a Fresenius Medical Care company

Danaher Corporation
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.