Comparison Overview
CareMed Specialty Pharmacy

CareMed Specialty Pharmacy
1985 Marcus Ave, Suite 130, New Hyde Park, NY, US, 11042
Last Update: 15/09/2026
At CareMed, we specialize in supporting patients living with rare, ultra-rare, and complex diseases by delivering the highest level of care through personalized support, clinical expertise, and close coordination throughout every phase of treatment. Navigating rare, ult...

Lonza
Muenchensteinerstr. 38, Basel, CH, 4002
Last Update: 13/09/2026
Lonza is a pioneer and world leader in the CDMO industry, setting the pace with cutting-edge science, smart technology, and lean manufacturing. United by a common purpose, we turn our customers’ breakthrough innovations into viable therapies and manufacture the medicine...
Compliance Ranges Comparison

CareMed Specialty Pharmacy







Lonza






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

CareMed Specialty Pharmacy

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