Comparison Overview
Beesafe sp. z o.o.

Beesafe sp. z o.o.
Aleje Jerozolimskie 181 b, Warszawa, 02-222, PL
Last Update: 27/03/2026
Beesafe to marka ubezpieczeniowa z internetowym charakterem. To co nas wyróżnia, to unikalne produkty ubezpieczeniowe oraz użyteczne usługi, z których chce się korzystać. Co więcej, każda zakupiona polisa i każdy dzień z nami zbliża Cię do zdobycia nagród dostarczanych ...

Canada Life
330 University Avenue, Toronto, M5G 1R8, CA
Last Update: 14/09/2026
At Canada Life, we’re focused on improving the financial, physical and mental well-being of Canadians. Whether handling policy claims, help growing and protecting clients’ retirement and investment savings, providing workplace mental health support for all employers or ...
Compliance Ranges Comparison

Beesafe sp. z o.o.







Canada Life






Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Beesafe sp. z o.o. in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Canada Life in 2026.
Incident History - Beesafe sp. z o.o. (X = Date, Y = Severity)
Beesafe sp. z o.o. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Canada Life (X = Date, Y = Severity)
Canada Life cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Beesafe sp. z o.o.

Canada Life
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.