Comparison Overview
Lövepac

Lövepac
4th Floor, Building 3 No. 21 Xingsheng Road , None, BDA, Beijing, CN, 100176
Last Update: 25/02/2026
Lövepac is a brand that is fully owned by Nolato - a group that has been established in 1938 and ever since has been making a difference. Particularly, the Lövepac was founded in 1968 in Skåne, South Sweden. The main inspiration for its creation was to provide a platfo...

Thermax Limited
IN, IN
Last Update: 23/09/2026
Incorporated in 1966, Thermax Group is a 1 billion US$ company headquartered in Pune, India. Over the years, it has grown into a leading conglomerate in the energy and environment space and a trusted partner in energy transition. Strategically spreading its operations ...
Compliance Ranges Comparison

Lövepac







Thermax Limited






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

Lövepac

Thermax Limited
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.