Comparison Overview
Rogers Communications

Rogers Communications
333 Bloor Street East, Toronto, M4W 1G9, CA
Last Update: 07/10/2026
Rogers is Canada’s communications and entertainment company, driven to connect and entertain Canadians. For more information, please visit rogers.com or investors.rogers.com. Déterminée à connecter et à divertir les Canadiens et Canadiennes, Rogers est la référence ...

airtel
Plot 16, Udyog Vihar Phase IV, Gurgaon, Haryana, IN, 122009
Last Update: 19/09/2026
Airtel was founded to provide global connectivity and unlock endless opportunities. Our organization embodies a unique blend of energy, innovation, creativity, dedication, scale, and ownership, all aimed at being limitless. At Airtel, we strive to go beyond our duties t...
Compliance Ranges Comparison

Rogers Communications







airtel






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
Rogers Communications has 64.84% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for airtel in 2026.
Incident History - Rogers Communications (X = Date, Y = Severity)
Rogers Communications cyber incidents detection timeline including parent company and subsidiaries.
Incident History - airtel (X = Date, Y = Severity)
airtel cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Rogers Communications

airtel
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.