Comparison Overview
Dignity Memorial

Dignity Memorial
1929 Allen Parkway , Houston, Texas, 77019, US
Last Update: 05/03/2026
As North America’s largest provider of funeral, cremation and cemetery services, the Dignity Memorial® network is the name families turn to for compassionate and professional final arrangements. Dignity Memorial providers care for more than 300,000 families each year a...

Home Instead
13323 California St, Omaha, NE, US, 68154
Last Update: 05/09/2026
As the world’s leading provider of in-home care, we help older adults live safely and independently at home, without sacrificing their quality of life. Whether they need occasional respite care or full-time support, our Care Pros are carefully selected to provide the be...
Compliance Ranges Comparison

Dignity Memorial







Home Instead






Benchmark & Cyber Underwriting Signals
Incidents vs Individual and Family Services Industry Avg (This Year)
No incidents recorded for Dignity Memorial in 2026.
Incidents vs Individual and Family Services Industry Avg (This Year)
No incidents recorded for Home Instead in 2026.
Incident History - Dignity Memorial (X = Date, Y = Severity)
Dignity Memorial cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Home Instead (X = Date, Y = Severity)
Home Instead cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Dignity Memorial

Home Instead
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.