Comparison Overview
Freedom Mobile

Freedom Mobile
88 Queens Quay W, Toronto, M5J 0B8, CA
Last Update: 28/03/2026
Freedom Mobile was founded on a simple pledge: Freedom from data overages and freedom from gouging. Instead you can count on flat monthly fees and affordable everything. We think that’s the kind of wireless freedom Canadians deserve. Our company’s culture reflects o...

PT. Indosat Tbk
Jl. Medan Merdeka Barat No. 21 Jakarta 10110, Indonesia, Jakarta Pusat, 10110, ID
Last Update: 19/09/2026
Indosat Ooredoo Hutchison (IDX: ISAT) ("IOH"), are here with our vision to become the most preferred digital telecommunications company of Indonesia. The IOH merger combines two highly complementary businesses between PT Indosat Tbk (“Indosat Ooredoo”) and PT Hutchison ...
Compliance Ranges Comparison

Freedom Mobile







PT. Indosat Tbk






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
Freedom Mobile has 45.05% fewer 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 PT. Indosat Tbk in 2026.
Incident History - Freedom Mobile (X = Date, Y = Severity)
Freedom Mobile cyber incidents detection timeline including parent company and subsidiaries.
Incident History - PT. Indosat Tbk (X = Date, Y = Severity)
PT. Indosat Tbk cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Freedom Mobile

PT. Indosat Tbk
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.