Comparison Overview
Corient

Corient
Miami, US
Last Update: 05/06/2026
Corient is the world’s largest non-bank wealth manager and multi-family office focused on serving ultra-high and high-net-worth individuals, families and businesses. We combine deeply personal service and local expertise with the resources of a global leader. Our unique...

Dubai Holding
Umm Suqeim Road, across from Madinat Jumeirah, Dubai, 66000 , AE
Last Update: 08/09/2026
Dubai Holding is a diversified global investment company that continues to power Dubai’s growth across 10 key sectors, including real estate, hospitality, leisure & entertainment, media, ICT, design, education, retail, manufacturing & logistics and science. Since 2004...
Compliance Ranges Comparison

Corient







Dubai Holding






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
Corient has 42.2% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Dubai Holding in 2026.
Incident History - Corient (X = Date, Y = Severity)
Corient cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Dubai Holding (X = Date, Y = Severity)
Dubai Holding cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Corient

Dubai Holding
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.