Comparison Overview
T-Mobile Polska Business Solutions 

T-Mobile Polska Business Solutions
ul. Marynarska 12, Warszawa, Mazowieckie, 02-674, PL
Last Update: 07/03/2026
We are a technology company providing advanced ICT solutions. Thanks to our cooperation with T-Mobile Poland, we are building a coherent business offer T Business, which responds to modern market needs and supports the digitisation processes of companies. We provide mob...

Inetum
5, Rue Touzet Gaillard, St.-Ouen, Île-de-France, FR, 93400
Last Update: 05/04/2026
Inetum is a European leader in digital services. Inetum’s team of 27,000 consultants and specialists strive every day to make a digital impact for businesses, public sector entities and society. Inetum’s solutions aim at contributing to its clients’ performance and inno...
Compliance Ranges Comparison

T-Mobile Polska Business Solutions







Inetum






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for T-Mobile Polska Business Solutions in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Inetum in 2026.
Incident History - T-Mobile Polska Business Solutions (X = Date, Y = Severity)
T-Mobile Polska Business Solutions cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Inetum (X = Date, Y = Severity)
Inetum cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

T-Mobile Polska Business Solutions

Inetum
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.