Comparison Overview
Terminix

Terminix
150 Peabody Pl- Terminix, Memphis, Tennessee, US, 38103
Last Update: 20/03/2026
Terminix is a leading provider of residential and commercial pest control. Terminix provides pest management services and protection against termites, mosquitoes, rodents, and other pests threatening human health and safety. Headquartered in Memphis, Tenn., Terminix ser...

Fosun 复星
600, ZHONGSHAN NO.2 ROAD(E) SHANGHAI, 200010 PRC, Shanghai, CN, 200010
Last Update: 01/04/2026
Fosun was founded in 1992. After more than 30 years of development, Fosun has become a global innovation-driven consumer group. Adhering to the mission of creating happier lives for families worldwide, Fosun is committed to creating a global happiness ecosystem fulfilli...
Compliance Ranges Comparison

Terminix







Fosun 复星






Benchmark & Cyber Underwriting Signals
Incidents vs Consumer Services Industry Avg (This Year)
No incidents recorded for Terminix in 2026.
Incidents vs Consumer Services Industry Avg (This Year)
No incidents recorded for Fosun 复星 in 2026.
Incident History - Terminix (X = Date, Y = Severity)
Terminix cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Fosun 复星 (X = Date, Y = Severity)
Fosun 复星 cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Terminix

Fosun 复星
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.