Comparison Overview
Technology Transfer Office (TTO) – Erasmus MC
Technology Transfer Office (TTO) – Erasmus MC
Wytemaweg 80, Faculteitsgebouw, Rotterdam, Zuid Holland, NL, 3015 CN
Last Update: 30/12/2025
TTO assists Erasmus MC employees on elements related to intellectual property valorization, from diagnostics and therapeutics to medical devices and innovations in care, so it can reach the patients.
Mercy Health
Cincinnati, 45237, US
Last Update: 13/09/2026
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 ...
Compliance Ranges Comparison
Technology Transfer Office (TTO) – Erasmus MC
Mercy Health
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Technology Transfer Office (TTO) – Erasmus MC in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Mercy Health in 2026.
Incident History - Technology Transfer Office (TTO) – Erasmus MC (X = Date, Y = Severity)
Technology Transfer Office (TTO) – Erasmus MC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mercy Health (X = Date, Y = Severity)
Mercy Health cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Technology Transfer Office (TTO) – Erasmus MC
Mercy Health
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout