Comparison Overview
SwiftWater - A TETRA Company
SwiftWater - A TETRA Company
2401 North County Road 1287, Midland, 79707, US
Last Update: 22/03/2026
On March 1, 2018, SwiftWater Energy Services was acquired by TETRA Technologies and operates under our Water and Flowback Services Division. Our SwiftWater brand in the Permian Basin delivers cost-effective water management solutions through unparalleled technical exper...
TotalEnergies
2, place Jean Millier - La Défense 6, Paris La Défense Cedex, 92078, FR
Last Update: 18/06/2026
Have you ever thought of offering your skills and expertise to a multinational company? Give your best to better energy and make the commitment with TotalEnergies. With over 500-plus professions in 130 countries, we offer high safety and environmental standards, stron...
Compliance Ranges Comparison
SwiftWater - A TETRA Company
TotalEnergies
Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for SwiftWater - A TETRA Company in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for TotalEnergies in 2026.
Incident History - SwiftWater - A TETRA Company (X = Date, Y = Severity)
SwiftWater - A TETRA Company cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TotalEnergies (X = Date, Y = Severity)
TotalEnergies cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
SwiftWater - A TETRA Company
TotalEnergies
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: *.*.