Comparison Overview
Millicom (Tigo)
Millicom (Tigo)
2 Rue du Fort Bourbon, Luxembourg, 1249, LU
Last Update: 05/07/2026
Millicom (NASDAQ U.S.: TIGO, Nasdaq) is a leading provider of fixed and mobile telecommunications services in Latin America. Through our TIGO® and Tigo Business® brands, we provide a wide range of digital services and products, including TIGO Money for mobile financial ...
Safaricom PLC
Waiyaki Way, Westlands, Nairobi, Nairobi, KE, P.O. Box 66827, 00800, Nairobi
Last Update: 19/05/2026
Safaricom is the leading provider of converged communication solutions in Kenya. In addition to providing a broad range of first-class products and services for Telephony, Broadband Internet and Financial services, Safaricom seeks to uplift the welfare of Kenyans throug...
Compliance Ranges Comparison
Millicom (Tigo)
Safaricom PLC
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Millicom (Tigo) in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Safaricom PLC in 2026.
Incident History - Millicom (Tigo) (X = Date, Y = Severity)
Millicom (Tigo) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Safaricom PLC (X = Date, Y = Severity)
Safaricom PLC cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Millicom (Tigo)
Safaricom PLC
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.