Comparison Overview
TotalEnergies Transport Solutions
TotalEnergies Transport Solutions
La Défense Cedex, Paris, FR
Last Update: 01/04/2026
Whether you’re a fleet owner, a logistics business, a public transport operator or a company specializing in passenger transport, TotalEnergies provides tailor-made solutions to meet all your transportation needs. We help you achieve your different objectives: offering...
Petrobras
Avenida República do Chile, n. 65, Centro, Rio de Janeiro, 20031-912, BR
Last Update: 02/07/2026
Nosso propósito é prover energia que assegure prosperidade de forma ética, justa, segura e competitiva. Queremos ser a melhor empresa diversificada e integrada de energia na geração de valor, construindo um mundo mais sustentável, conciliando o foco em óleo e gás com a ...
Compliance Ranges Comparison
TotalEnergies Transport Solutions
Petrobras
Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for TotalEnergies Transport Solutions in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Petrobras in 2026.
Incident History - TotalEnergies Transport Solutions (X = Date, Y = Severity)
TotalEnergies Transport Solutions cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Petrobras (X = Date, Y = Severity)
Petrobras cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
TotalEnergies Transport Solutions
Petrobras
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: *.*.