Comparison Overview
Interislander

Interislander
2 Bunny Street, Wellington, 6011, NZ
Last Update: 07/07/2026
Proudly New Zealand's original Cook Strait ferry - Interislander has been connecting the North and South Islands for over 60 years! Along with the breathtaking views, enjoy our locally sourced food and beverages, cinema's, free kids activities and premium lounges on bo...

Royal Caribbean Group
Royal Caribbean Group 1050 Caribbean Way Miami, Miami, Florida, US, 2312
Last Update: 17/09/2026
At Royal Caribbean Group, we deliver unforgettable vacations to guests who trust us with life’s greatest moments. We build the best ships, and even better careers, all while doing the right thing. We are passionate. We are innovative. We are unstoppable. We open the wor...
Compliance Ranges Comparison

Interislander







Royal Caribbean Group






Benchmark & Cyber Underwriting Signals
Incidents vs Travel Arrangements Industry Avg (This Year)
No incidents recorded for Interislander in 2026.
Incidents vs Travel Arrangements Industry Avg (This Year)
No incidents recorded for Royal Caribbean Group in 2026.
Incident History - Interislander (X = Date, Y = Severity)
Interislander cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Royal Caribbean Group (X = Date, Y = Severity)
Royal Caribbean Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Interislander

Royal Caribbean Group
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.