Comparison Overview
EBSCO Health Care

EBSCO Health Care
10 Estes St, Ipswich, 01938, US
Last Update: 18/02/2026
EBSCO Information Services is the leading provider of evidence-based clinical decision support solutions, shared decision-making resources, health care business intelligence and peer-reviewed medical research information.

Dignity Health
185 Berry St, San Francisco, 94158, US
Last Update: 12/06/2026
We provide quality, compassionate health care at more than 40 hospitals and care centers that are serving communities across California, Arizona and Nevada every minute of every day. And while not everyone may live near a major medical facility, Dignity Health is making...
Compliance Ranges Comparison

EBSCO Health Care







Dignity Health






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

EBSCO Health Care

Dignity 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