Comparison Overview
CuraScript SD by Evernorth

CuraScript SD by Evernorth
255 Technology Park, Lake Mary, 32746, US
Last Update: 25/02/2026
More than a specialty distributor At our core, CuraScript SD provides integrated delivery solutions for the safe and efficient distribution of specialty pharmaceuticals and associated medical supplies. We’ve been caring for those who care for more than a quarter of a ce...

Catalent
101 E Kennedy Blvd, Tampa, Florida, US, 33602
Last Update: 12/09/2026
Championing the missions that matter™. Catalent, Inc. is a leading global contract development and manufacturing organization (CDMO) and trusted partner to pharma, biotech, and consumer health companies worldwide. We put patients first in everything we do, helping peopl...
Compliance Ranges Comparison

CuraScript SD by Evernorth







Catalent






Benchmark & Cyber Underwriting Signals
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for CuraScript SD by Evernorth in 2026.
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for Catalent in 2026.
Incident History - CuraScript SD by Evernorth (X = Date, Y = Severity)
CuraScript SD by Evernorth cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Catalent (X = Date, Y = Severity)
Catalent cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

CuraScript SD by Evernorth

Catalent
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.