Comparison Overview
Johnson Controls Fire Suppression

Johnson Controls Fire Suppression
N/A
Last Update: 14/11/2025
Johnson Controls Fire Suppression is a global leader of fire suppression solutions and services, ranging from extinguishing agents to sprinkler systems. With a strong focus on safety and protection, our company offers innovative, sustainable technologies such as, clean ...

Wärtsilä
Hiililaiturinkuja 2, Helsinki, 00180, FI
Last Update: 23/09/2026
We are a global leader in innovative technologies and services shaping the decarbonisation of marine and energy. With approximately 6.9 billion euros in sales and 18,000 employees across 78 countries, the Wärtsilä strategy focuses on helping customers to continuously im...
Compliance Ranges Comparison

Johnson Controls Fire Suppression







Wärtsilä






Benchmark & Cyber Underwriting Signals
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Johnson Controls Fire Suppression in 2026.
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Wärtsilä in 2026.
Incident History - Johnson Controls Fire Suppression (X = Date, Y = Severity)
Johnson Controls Fire Suppression cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Wärtsilä (X = Date, Y = Severity)
Wärtsilä cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Johnson Controls Fire Suppression

Wärtsilä
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.