Comparison Overview
Parker Lord

Parker Lord
111 LORD Drive, Cary, 27511, US
Last Update: 27/01/2026
Parker Hannifin, a Fortune 250 global leader in motion and control technologies. For more than 100 years, the Parker has engineered the success of its customers in a wide range of diversified industrial and aerospace markets. The company's products are vital to virtual...

GEA Group
Ulmenstraße 99, Düsseldorf, 40476, DE
Last Update: 23/09/2026
GEA is one of the largest technology suppliers for food processing and a wide range of other industries. The global group specializes in machinery, plants, as well as process technology and components. GEA provides resource-efficient solutions for sophisticated product...
Compliance Ranges Comparison

Parker Lord







GEA Group






Benchmark & Cyber Underwriting Signals
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Parker Lord in 2026.
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for GEA Group in 2026.
Incident History - Parker Lord (X = Date, Y = Severity)
Parker Lord cyber incidents detection timeline including parent company and subsidiaries.
Incident History - GEA Group (X = Date, Y = Severity)
GEA Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Parker Lord

GEA Group
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.