Comparison Overview
Grameenphone Ltd

Grameenphone Ltd
Bashundhara, Baridhara, Dhaka, undefined, 1229, BD
Last Update: 26/04/2026
The right and contemporary use of technology is key to the progress of a nation. Keeping this in mind, Grameenphone always brings future-proof technology in order to facilitate your progress. The possibilities in this new world are immense and someone as bright as you s...

Deutsche Telekom
Friedrich-Ebert-Allee 140, Bonn, 53113, DE
Last Update: 24/09/2026
Welcome to Deutsche Telekom. As one of the world's most valuable brands, we design innovative solutions and products in the areas of connectivity, networks, digitalization and security. #connectingyourworld At Deutsche Telekom, we believe that each and every one of us...
Compliance Ranges Comparison

Grameenphone Ltd







Deutsche Telekom






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

Grameenphone Ltd

Deutsche Telekom
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)