Comparison Overview
Telekom HU
Telekom HU
Könyves Kálmán krt. 36, Budapest, Pest megye, HU, 1097
Last Update: 18/02/2026
A Telekom a digitális optimistákat keresi, akik - álljon bármilyen szám is az anyakönyvi kivonatukban - hisznek benne, hogy a digitális technológia a fejlődés motorja, melynek állandó változásával együtt ők is képesek megújulni, épp úgy, ahogy a Telekom is folyamatosan ...
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
Telekom HU
Rogers Communications
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Telekom HU in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
Rogers Communications has 83.49% more incidents than the average of all companies with at least one recorded incident.
Incident History - Telekom HU (X = Date, Y = Severity)
Telekom HU 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
Telekom HU
Rogers Communications
FAQ
Latest Global CVEs
clash-verge-service-ipc before 2.3.0 has a world-reachable IPC endpoint, leading to local privilege escalation.
A vulnerability was identified in theonedev onedev up to 15.0.5. This vulnerability affects the function canAccessIssue of the file /issues/ of the component Pull Request Handler. Such manipulation of the argument issue leads to improper authorization. It is possible to launch the attack remotely. Upgrading to version 15.0.6 is able to resolve this issue. It is advisable to upgrade the affected component.
A vulnerability was determined in theonedev onedev up to 15.0.5. This affects an unknown part of the file /repositories/{projectId}/default-branch of the component REST API. This manipulation of the argument project.defaultBranch causes improper authorization. It is possible to initiate the attack remotely. Upgrading to version 15.0.6 is able to mitigate this issue. Upgrading the affected component is advised.
A vulnerability was found in theonedev onedev up to 15.0.5. Affected by this issue is some unknown functionality of the file /projects/ of the component Parent Project Handler. The manipulation of the argument project.parentId results in improper authorization. The attack may be performed from remote. Upgrading to version 15.0.6 can resolve this issue. It is recommended to upgrade the affected component.
A vulnerability has been found in theonedev onedev up to 15.0.5. Affected by this vulnerability is an unknown functionality of the file /projects. The manipulation of the argument project.forkedFromId leads to improper authorization. The attack is possible to be carried out remotely. Upgrading to version 15.0.6 addresses this issue. Upgrading the affected component is recommended.