Comparison Overview
Capgemini Engineering
Capgemini Engineering
76, Avenue Kléber, Paris, Île-de-France, FR, 75116
Last Update: 01/04/2026
World leader in engineering and R&D services, Capgemini Engineering combines its broad industry knowledge and cutting-edge technologies in digital and software to support the convergence of the physical and digital worlds. Coupled with the capabilities of the rest of th...
ST Engineering
ST Engineering Hub, Singapore, 567710, SG
Last Update: 30/03/2026
At ST Engineering, we apply our technology and innovation to solve real-world problems and improve lives. Our commitment to excellence and our track record as a global technology, defence, and engineering company earns us a reputation for quality and trust. Subsc...
Compliance Ranges Comparison
Capgemini Engineering
ST Engineering
Benchmark & Cyber Underwriting Signals
Incidents vs Engineering Services Industry Avg (This Year)
No incidents recorded for Capgemini Engineering in 2026.
Incidents vs Engineering Services Industry Avg (This Year)
No incidents recorded for ST Engineering in 2026.
Incident History - Capgemini Engineering (X = Date, Y = Severity)
Capgemini Engineering cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ST Engineering (X = Date, Y = Severity)
ST Engineering cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Capgemini Engineering
ST Engineering
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: *.*.