Comparison Overview
Gentiva

Gentiva
3350 Riverwood Pkwy, Atlanta, 30339, US
Last Update: 03/04/2026
At Gentiva, it is our privilege to offer compassionate care that’s close to home – and close to the heart. We are a close-knit family of industry-leading hospice, palliative, and home health providers. Our place is by the side of those who need us – from helping people ...

AdventHealth
900 Hope Way, Altamonte Springs, 32714, US
Last Update: 03/09/2026
AdventHealth is a connected network of care that helps people feel whole – body, mind and spirit. More than 100,000 team members across a national footprint provide whole-person care to nearly nine million people annually through more than 2,000 care sites that include ...
Compliance Ranges Comparison

Gentiva







AdventHealth






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

Gentiva

AdventHealth
FAQ
Latest Global CVEs
Heym from 0.0.55 before 0.0.121 contains a privilege escalation vulnerability that allows shared collaborators to overwrite a workflow's error_workflow_id because the field is missing from OWNER_ONLY_EXECUTION_FIELDS. Attackers can point the error workflow to their own workflow with an HTTP node, and when the parent workflow errors the owner's decrypted credentials are injected and exfiltrated.
Nodemailer from 3.0.0 before 10.0.10 contains a quadratic complexity denial of service vulnerability in the SMTP client reply parser in SMTPConnection._onData and isPartialResponse. A malicious SMTP server or on-path attacker can stream continuation lines without a completion line before authentication, blocking the Node.js event loop and exhausting memory.
Nodemailer from 3.0.0 before 10.0.10 contains a denial of service vulnerability in MessageParser.parseHeaders that allows users to exhaust CPU through quadratic header unfolding. Attackers can supply large recipient lists or long headers that fold into tens of thousands of continuation lines, blocking the Node.js event loop during DKIM signing.
Nodemailer from 3.0.0 before 10.0.13 contains an improper input validation vulnerability in its address parser that fails to strip RFC 5322 comments inside angle-bracket addresses. Attackers can supply recipients like a display name with a parenthesized comment in the domain, so illegal characters reach envelope.to and RCPT TO, causing rejected delivery or parser interpretation conflicts that bypass domain allow-lists.
Nodemailer 3.0.0 before 10.0.13 has a regular expression denial of service in SMTPConnection._actionEHLO, whose four AUTH mechanism detection regexes contain overlapping whitespace sub-patterns that backtrack quadratically. A malicious or man-in-the-middle SMTP server can reply to EHLO with 250-AUTH, a long whitespace run and a non-matching token, blocking the Node.js event loop for tens of seconds to hours before authentication.