Comparison Overview
3Shape Poland

3Shape Poland
Południowa, Szczecin, zachodniopomorskie, 71-001, PL
Last Update: 28/04/2026
3Shape Poland to dynamiczne centrum technologiczne, w którym rozwijamy przełomowe rozwiązania dla branży stomatologicznej. Jesteśmy częścią globalnej firmy 3Shape, lidera w dziedzinie cyfrowej stomatologii, a nasz zespół w Polsce łączy inżynierię, IT i produkcję, dostar...

Baxter International Inc.
1 Baxter Pkwy, Deerfield, 60015, US
Last Update: 14/09/2026
For nearly a century, we have delivered on our commitment to saving and sustaining the lives of patients, working alongside clinicians and providers around the world. We believe every person — regardless of who they are or where they are from — deserves a chance to live...
Compliance Ranges Comparison

3Shape Poland







Baxter International Inc.






Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for 3Shape Poland in 2026.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
Baxter International Inc. has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - 3Shape Poland (X = Date, Y = Severity)
3Shape Poland cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Baxter International Inc. (X = Date, Y = Severity)
Baxter International Inc. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

3Shape Poland

Baxter International Inc.
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.