Comparison Overview
Vertiv Hong Kong

Vertiv Hong Kong
Suites 1501-04, 15/F, 625 King's Road, Hong Kong, HK
Last Update: 07/01/2026
Vertiv is a global leader in critical digital infrastructure for applications in data centers, communication networks, and commercial and industrial environments. As businesses, industries, and communities become more connected, we pioneer and deliver end-to-end power...

Foxconn
US
Last Update: 23/09/2026
Established in Taiwan in 1974, Hon Hai Technology Group (Foxconn) (2317: Taiwan) is the world’s largest electronics manufacturer. Foxconn is also the leading technological solution provider, and it continuously leverages its expertise in software and hardware to integra...
Compliance Ranges Comparison

Vertiv Hong Kong







Foxconn






Benchmark & Cyber Underwriting Signals
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Vertiv Hong Kong in 2026.
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
Foxconn has 292.16% more incidents than the average of all companies with at least one recorded incident.
Incident History - Vertiv Hong Kong (X = Date, Y = Severity)
Vertiv Hong Kong cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Foxconn (X = Date, Y = Severity)
Foxconn cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Vertiv Hong Kong

Foxconn
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.