Comparison Overview
GSMA Open Gateway
GSMA Open Gateway
London, GB
Last Update: 27/12/2025
Welcome to the GSMA Open Gateway community! We invite you to delve into the exciting landscape of universal mobile network APIs that are revolutionising the way developers access operator networks. Stay updated on transformative industry shifts in telecom service desi...
Vivo (Telefônica Brasil)
Avenida Eng. Luís Carlos Berrini, 1376, São Paulo, 04571 - 000, BR
Last Update: 01/04/2026
Vivo (Telefônica Brasil) is part of the Telefónica Group and with more than 94 million customers, of which 75 million mobile and 19 million fixed, we are the largest telecommunications company in Brazil, with nationwide presence and a complete, convergent portfolio of p...
Compliance Ranges Comparison
GSMA Open Gateway
Vivo (Telefônica Brasil)
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for GSMA Open Gateway in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Vivo (Telefônica Brasil) in 2026.
Incident History - GSMA Open Gateway (X = Date, Y = Severity)
GSMA Open Gateway cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Vivo (Telefônica Brasil) (X = Date, Y = Severity)
Vivo (Telefônica Brasil) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
GSMA Open Gateway
Vivo (Telefônica Brasil)
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: *.*.