Comparison Overview
Seagate Technology

Seagate Technology
47488 Kato Rd, Fremont, CA, US, 94538
Last Update: 13/09/2026
Seagate is a leader in mass-capacity data storage. We’ve delivered more than four and a half billion terabytes of capacity over the past four decades. We make storage that scales, bringing trust and integrity to innovations that depend on data. In an era of unprecedente...

Quanta Computer Inc. 廣達電腦
TW
Last Update: 26/09/2026
Established in 1988, Quanta Computer is the largest notebook computer ODM company in the world. With leading technology and strong R&D capability, Quanta has become a leader in hi-tech markets and the best partner providing quality design and manufacturing services to t...
Compliance Ranges Comparison

Seagate Technology







Quanta Computer Inc. 廣達電腦






Benchmark & Cyber Underwriting Signals
Incidents vs Computer Hardware Manufacturing Industry Avg (This Year)
No incidents recorded for Seagate Technology in 2026.
Incidents vs Computer Hardware Manufacturing Industry Avg (This Year)
No incidents recorded for Quanta Computer Inc. 廣達電腦 in 2026.
Incident History - Seagate Technology (X = Date, Y = Severity)
Seagate Technology cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Quanta Computer Inc. 廣達電腦 (X = Date, Y = Severity)
Quanta Computer Inc. 廣達電腦 cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Seagate Technology

Quanta Computer Inc. 廣達電腦
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.