Comparison Overview
COMO Hotels and Resorts

COMO Hotels and Resorts
COMO House, Singapore, Singapore, 258332, SG
Last Update: 01/06/2026
COMO Hotels and Resorts is committed to creating extraordinary experiences for curious people with a passion for a life lived fully. Our properties, from Bhutan to London, draw their inspiration from compelling locations. To this we bring the expertise for nurturing min...

DoubleTree by Hilton
7930 Jones Branch Drive, McLean, US
Last Update: 08/09/2026
DoubleTree by Hilton hotels are distinctively designed properties that provide true comfort to today’s business and leisure travelers. From the millions of delighted hotel guests who are welcomed with the brand’s legendary, warm chocolate chip cookies at check-in to the...
Compliance Ranges Comparison

COMO Hotels and Resorts







DoubleTree by Hilton






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for COMO Hotels and Resorts in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for DoubleTree by Hilton in 2026.
Incident History - COMO Hotels and Resorts (X = Date, Y = Severity)
COMO Hotels and Resorts cyber incidents detection timeline including parent company and subsidiaries.
Incident History - DoubleTree by Hilton (X = Date, Y = Severity)
DoubleTree by Hilton cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

COMO Hotels and Resorts

DoubleTree by Hilton
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.