Comparison Overview
MasterCorp, Inc.

MasterCorp, Inc.
4700 MILLENIA BLVD, ORLANDO, 32839-6018, US
Last Update: 31/03/2026
With over 45 years of experience, MasterCorp has proudly served as a trusted partner in the hospitality services industry. At the heart of our success is our People Proud culture, where Associates are at the center of every decision we make and the driving force behind ...

Radisson Hotel Group
44 Avenue du Bourget, Brussels, B-1130, BE
Last Update: 15/09/2026
Radisson Hotel Group is an international hotel group, operating in EMEA and APAC with over 1,320 hotels in operation and under development in +95 countries. The international hotel group is rapidly expanding with a plan to significantly grow the portfolio. The Group’s o...
Compliance Ranges Comparison

MasterCorp, Inc.







Radisson Hotel Group






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for MasterCorp, Inc. in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Radisson Hotel Group in 2026.
Incident History - MasterCorp, Inc. (X = Date, Y = Severity)
MasterCorp, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Radisson Hotel Group (X = Date, Y = Severity)
Radisson Hotel Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

MasterCorp, Inc.

Radisson Hotel 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.