Comparison Overview
Capgemini Telecommunications
Capgemini Telecommunications
l'Étoile - 11 rue de Tilsitt , Paris, 75017, FR
Last Update: 17/12/2025
The telecom industry stands at a pivotal moment. As fiber and 5G infrastructure builds begin to wind down, telco organizations and network operators are left asking: What’s next? Now is the time to let imagination shape a new era for telecom, driven by transformative i...
Deutsche Telekom
Friedrich-Ebert-Allee 140, Bonn, Germany, DE, 53113
Last Update: 03/07/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
Capgemini Telecommunications
Deutsche Telekom
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Capgemini Telecommunications in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
Deutsche Telekom has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Capgemini Telecommunications (X = Date, Y = Severity)
Capgemini Telecommunications 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
Capgemini Telecommunications
Deutsche Telekom
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: *.*.