Comparison Overview
Ooredoo Group

Ooredoo Group
100 West Bay, Doha, Doha, QA, Po Box 217
Last Update: 01/04/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 ...

Rogers Communications
333 Bloor Street East, Toronto, Ontario, CA, M4W 1G9
Last Update: 01/04/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 ...
Compliance Ranges Comparison

Ooredoo Group







Rogers Communications






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

Ooredoo Group

Rogers Communications
FAQ
Latest Global CVEs
Fides is an open-source privacy engineering platform. From version 2.33.0 to before version 2.84.5, there is a DOM-based XSS vulnerability in fides.js via the fides_description override. This issue has been patched in version 2.84.5.
WACRM prior to commit 73041bf contain an authorization bypass vulnerability in the automation engine that allows authenticated attackers to access and modify contacts belonging to other tenants by supplying an arbitrary caller-controlled contact_id in the POST request body without tenant ownership verification. Attackers can exploit the service-role client that bypasses row-level security to modify victim contact fields including name, email, and company across tenant boundaries using only a known contact UUID.
Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
When ALLOW_INSECURE_RAW_TEXT is enabled, whitespace-variant closing tags (e.g., </style\t>) are not recognized by the sanitizer but accepted by browsers as valid end tags, allowing subsequent content to escape sanitization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
Headplane is a feature-complete Web UI for Headscale. Prior to versions 0.6.3 and 0.7.0-beta.3, Headplane was vulnerable to a path traversal / authorization bypass in the Headscale API client used by node and user rename operations. This issue has been patched in versions 0.6.3 and 0.7.0-beta.3.