Comparison Overview
Desert Care Network

Desert Care Network
1150 N Indian Canyon Dr, Palm Springs, 92262, US
Last Update: 04/04/2026
The compassionate, personalized care you already know is now backed by an even larger network of resources, expertise, innovation, and locations across the desert region. Desert Regional Medical Center joined with Hi-Desert Medical Center and JFK Memorial Hospital to c...

Cardinal Health
7000 Cardinal Place, Dublin, OH, US, 43017
Last Update: 07/10/2026
Cardinal Health is a distributor of pharmaceuticals and specialty products; a supplier of home-health and direct-to-patient products and services; an operator of nuclear pharmacies and manufacturing facilities; a provider of performance and data solutions; and a global ...
Compliance Ranges Comparison

Desert Care Network







Cardinal Health






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Desert Care Network in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Cardinal Health in 2026.
Incident History - Desert Care Network (X = Date, Y = Severity)
Desert Care Network cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Cardinal Health (X = Date, Y = Severity)
Cardinal Health cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Desert Care Network

Cardinal Health
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.