Comparison Overview
Deutsche Telekom Investor Relations

Deutsche Telekom Investor Relations
Friedrich-Ebert Allee 140, Bonn, 53113, DE
Last Update: 20/01/2026
Welcome to the official Investor Relations LinkedIn page of Deutsche Telekom! Click "Follow" to keep up-to-date on: 1. Our latest business and financial achievements, 2. Upcoming events and key takeaways, 3. Insightful updates and discussions about Deutsche Telekom's s...

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 ...
Compliance Ranges Comparison

Deutsche Telekom Investor Relations







Ooredoo Group






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Deutsche Telekom Investor Relations in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Ooredoo Group in 2026.
Incident History - Deutsche Telekom Investor Relations (X = Date, Y = Severity)
Deutsche Telekom Investor Relations 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

Deutsche Telekom Investor Relations

Ooredoo Group
FAQ
Latest Global CVEs
A vulnerability was identified in ealpha072 Student-Management-System up to 01451bd7a2f58cdda07bd0b86e3967582e3ecd08. Affected by this issue is some unknown functionality of the file admin/config.php of the component Administrative Backend. Such manipulation leads to improper authentication. The attack may be performed from remote. The exploit is publicly available and might be used. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed. The project was informed of the problem early through an issue report but has not responded yet.
A vulnerability was determined in sgl-project SGLang up to 0.5.11. Affected by this vulnerability is the function data_hash of the component Cache Handler. This manipulation causes denial of service. The attack is restricted to local execution. A high degree of complexity is needed for the attack. The exploitation appears to be difficult. The exploit has been publicly disclosed and may be utilized. The pull request to fix this issue awaits acceptance.
Active IQ OneCollect version 2.7.3 contains hard-coded credentials that could allow an authenticated attacker with low privileges to perform unauthorized AutoSupport operations.
Active IQ Config Advisor version 6.7.3 contains hard-coded credentials that could allow an authenticated attacker with low privileges to perform unauthorized AutoSupport operations.
A vulnerability was found in crmeb crmeb_java 1.4. Affected is the function RestTemplate.getForEntity of the file crmeb-common/src/main/java/com/zbkj/common/utils/RestTemplateUtil.java of the component base64 Qrcode Endpoint. The manipulation of the argument url results in server-side request forgery. The attack can be executed remotely. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.