Comparison Overview
T-Mobile Czech Republic a.s.

T-Mobile Czech Republic a.s.
Tomíčkova 2144/1, Praha 4, CZ, 148 00
Last Update: 06/03/2026
T-Mobile Czech Republic, člen mezinárodní telekomunikační skupiny Deutsche Telekom, je téměř se 6,5 milionu mobilních zákazníků jedničkou na českém trhu. Jsme dokonale integrovaným mobilním operátorem a kromě telekomunikačních služeb nabízíme také komplexní ICT řešení p...

Telefónica
Spain, Madrid, 28050, ES
Last Update: 12/05/2026
Telefónica is today one of the largest telecommunications companies in the world in terms of market capitalisation and number of customers. We have the best infrastructure, as well as an innovative range of digital and data services; therefore, we are favorably position...
Compliance Ranges Comparison

T-Mobile Czech Republic a.s.







Telefónica






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for T-Mobile Czech Republic a.s. in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Telefónica in 2026.
Incident History - T-Mobile Czech Republic a.s. (X = Date, Y = Severity)
T-Mobile Czech Republic a.s. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Telefónica (X = Date, Y = Severity)
Telefónica cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

T-Mobile Czech Republic a.s.

Telefónica
FAQ
Latest Global CVEs
An authenticated user with the read role may read limited amounts of uninitialized stack memory via specially-crafted issuances of the filemd5 command
The $_internalApplyOplogUpdate aggregation pipeline stage can be used to execute a document diff containing a malformed binary diff to return memory out-of-bounds or crash the server. $_internalApplyOplogUpdate can be executed by any authenticated user with access to the aggregate command.
An authorized user could trigger a server crash by running a query with a 2dsphere index on a field that stores a GeoJSON GeometryCollection containing a Polygon with a strict-winding CRS. Strict-winding polygons are intentionally unsupported for indexing, but the guard that rejects them does not inspect members of a GeometryCollection, allowing the unsafe path to be reached which ends with an ensuing null-pointer dereference.
The ldapQueryPassword parameter, when set through the runtime setParameter command, will log the new password to the mongod.log file in plain text.
An authenticated user can cause a MongoDB server to crash or return incorrect results by creating documents that interfere with internal metadata processing during query execution. This stems from insufficient separation between user-controlled document fields and internal metadata in certain execution paths.