Comparison Overview
Kepler Communications Inc.

Kepler Communications Inc.
24 Ward St, Toronto, M6H 4A6, CA
Last Update: 17/03/2026
We are delivering on-orbit data at lightspeed with a constellation of satellites designed to act as Internet exchange points for space-to-space data relay. Headquartered in downtown Toronto, Kepler is vertically integrated with an in-house production facility, designin...

Ooredoo Group
100 West Bay, Doha, Doha, QA, Po Box 217
Last Update: 05/09/2026
We are an award-winning international communications company operating across the Middle East, North Africa and Southeast Asia. Serving consumers and businesses in 10 countries, we deliver a leading data experience through a broad range of content and services via ...
Compliance Ranges Comparison

Kepler Communications Inc.







Ooredoo Group






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

Kepler Communications Inc.

Ooredoo Group
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.