Comparison Overview
MAN Diesel & Turbo

MAN Diesel & Turbo
Stadtbachstrasse 1, Augsburg, undefined, D-86153, DE
Last Update: 02/12/2025
MAN Energy Solutions enables its customers to achieve sustainable value creation in the transition towards a carbon neutral future. Addressing tomorrow’s challenges within the marine, energy and industrial sectors, we improve efficiency and performance at a systemic lev...

Trane Technologies
Davidson, US
Last Update: 23/09/2026
Trane Technologies is a global climate innovator advancing sustainability through our leading brands Trane® and Thermo King®, which bring efficient and sustainable climate solutions to buildings, homes and transportation across the globe. Together, we are one team innov...
Compliance Ranges Comparison

MAN Diesel & Turbo







Trane Technologies






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

MAN Diesel & Turbo

Trane Technologies
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.