Comparison Overview
Jungheinrich Chile

Jungheinrich Chile
Miraflores 9699, Pudahuel, CL
Last Update: 28/11/2025
Jungheinrich es una multinacional alemana fundada en 1953 por el Dr. Friedrich Jungheinrich con sede central en Hamburgo, Alemania. Dedicada a las soluciones intralogísticas completas, Jungheinrich orienta su gama de productos y servicios a desarrollar una planificación...

Lineage
46500 Humboldt Dr., Novi, MI, US, 48377
Last Update: 13/09/2026
Lineage is one of the world’s leading temperature-controlled industrial REITs and integrated solutions providers with a global network of over 480 strategically located facilities, totaling nearly 2.9 billion cubic feet of capacity across countries in North America, Eur...
Compliance Ranges Comparison

Jungheinrich Chile







Lineage






Benchmark & Cyber Underwriting Signals
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for Jungheinrich Chile in 2026.
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for Lineage in 2026.
Incident History - Jungheinrich Chile (X = Date, Y = Severity)
Jungheinrich Chile cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lineage (X = Date, Y = Severity)
Lineage cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Jungheinrich Chile

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