Comparison Overview
Bupa Dental Care Australia

Bupa Dental Care Australia
Lane Cove, 2066, AU
Last Update: 27/02/2026
As part of our commitment to help make a difference to the health and care of our customers, we have taken a more active role to provide health and care services to help our customers achieve and maintain optimal health. Oral health is one of the cornerstones of overal...

Life Time Inc.
2902 Corporate Place, Chanhassen, MN, US, 55317
Last Update: 31/03/2026
Life Time provides an entertaining, educational, friendly and inviting, functional and innovative experience of uncompromising quality that meets the health and fitness needs of the entire family. Life Time is a wellness pioneer reshaping the way consumers approach the...
Compliance Ranges Comparison

Bupa Dental Care Australia







Life Time Inc.






Benchmark & Cyber Underwriting Signals
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for Bupa Dental Care Australia in 2026.
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for Life Time Inc. in 2026.
Incident History - Bupa Dental Care Australia (X = Date, Y = Severity)
Bupa Dental Care Australia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Life Time Inc. (X = Date, Y = Severity)
Life Time Inc. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Bupa Dental Care Australia

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