Comparison Overview
Viettel Group
Viettel Group
Lô D26, Khu đô thị mới Cầu Giấy, Yên Hòa, Hà Nội , Hà Nội, 1000064, VN
Last Update: 25/02/2026
Viettel is growing fast and disrupting markets across the region. To succeed, we want to attract the most forward-thinking employees, ones who aren’t afraid to be entrepreneurial, embrace risks, and create a new kind of company. Viettel Group is one of the world’s fast...
SLB
5599 San Felipe St, Houston, Texas, US, 77056
Last Update: 21/05/2026
We are a technology company that unlocks access to energy for the benefit of all. As innovators, that’s been our mission for nearly a century. Today, we face a global imperative to create a future with more energy, but less carbon. Our diverse, innovative change makers ...
Compliance Ranges Comparison
Viettel Group
SLB
Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Viettel Group in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for SLB in 2026.
Incident History - Viettel Group (X = Date, Y = Severity)
Viettel Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SLB (X = Date, Y = Severity)
SLB cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Viettel Group
SLB
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: *.*.