Comparison Overview
Amphenol

Amphenol
358 Hall Ave, Wallingford, Connecticut, 06492, US
Last Update: 29/03/2026
Amphenol is one of the largest manufacturers on the planet you’ve never heard of. Founded in 1932 and headquartered out of Connecticut, Amphenol is a Fortune 500 company with more than 90,000 employees throughout the world. Our products are a key ingredient in the elect...

Haier
1 Haier Rd, Laoshan District., Qingdao, 266103, CN
Last Update: 24/09/2026
Established in 1984, Haier Group is a world-leading provider of solutions to better life. Focusing on user experience, Haier has been included on the list of BrandZ™ Top 100 Most Valuable Global Brands for two consecutive years as the world’s first and only IoT ecosyste...
Compliance Ranges Comparison

Amphenol







Haier






Benchmark & Cyber Underwriting Signals
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Amphenol in 2026.
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Haier in 2026.
Incident History - Amphenol (X = Date, Y = Severity)
Amphenol cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Haier (X = Date, Y = Severity)
Haier cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Amphenol

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