Comparison Overview
Cogeco Inc.

Cogeco Inc.
1, Place Ville-Marie, Montreal, H3B 3N2, CA
Last Update: 09/06/2026
Rooted in the communities it serves, Cogeco Inc. is a growing competitive force in the North American telecommunications and media sectors with a legacy of more than 65 years. Through its business units Cogeco Connexion and Breezeline, Cogeco Communications provides Int...

ZTE Corporation
ZTE Corporation Hi-Tech Road South, Shenzhen, 518057, CN
Last Update: 07/09/2026
ZTE connects the world with continuous innovation for a better future. The company provides innovative technologies and integrated solutions, and its portfolio spans communication networks, computing infrastructure, industry digital solutions, and personal and home sm...
Compliance Ranges Comparison

Cogeco Inc.







ZTE Corporation






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Cogeco Inc. in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for ZTE Corporation in 2026.
Incident History - Cogeco Inc. (X = Date, Y = Severity)
Cogeco Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ZTE Corporation (X = Date, Y = Severity)
ZTE Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Cogeco Inc.

ZTE Corporation
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.