Comparison Overview
Beeline Kyrgyzstan

Beeline Kyrgyzstan
N/A
Last Update: 20/12/2025
Делая связь частью жизни, мы открываем доступ к информации, общению и даем кыргызстанцам безграничные возможности для развития страны и общества.

Deutsche Telekom
Friedrich-Ebert-Allee 140, Bonn, Germany, DE, 53113
Last Update: 15/05/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

Beeline Kyrgyzstan







Deutsche Telekom






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Beeline Kyrgyzstan in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
Deutsche Telekom has 7.41% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Beeline Kyrgyzstan (X = Date, Y = Severity)
Beeline Kyrgyzstan 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

Beeline Kyrgyzstan

Deutsche Telekom
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.