Comparison Overview
EXL Data Management
EXL Data Management
10 Exchange Place, New Jersey City, New Jersey, 07302, US
Last Update: 08/03/2026
Data Management by EXL specializes in Enterprise Data Management, Data Integration and Business Intelligence (BI). We are experts in data architecture, modeling, integration, virtualization, quality, MDM, metadata management, data visualization, mobile analytics, analy...
Computacenter
Hatfield Avenue, Hatfield, Hertfordshire, GB, AL10 9TW
Last Update: 02/04/2026
Computacenter is a leading independent technology and services provider, trusted by large corporate and public sector organisations. We are a responsible business that believes in winning together for our people and our planet. We help our customers to Source, Tran...
Compliance Ranges Comparison
EXL Data Management
Computacenter
Benchmark & Cyber Underwriting Signals
Incidents vs Information Technology & Services Industry Avg (This Year)
No incidents recorded for EXL Data Management in 2026.
Incidents vs Information Technology & Services Industry Avg (This Year)
No incidents recorded for Computacenter in 2026.
Incident History - EXL Data Management (X = Date, Y = Severity)
EXL Data Management cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Computacenter (X = Date, Y = Severity)
Computacenter cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
EXL Data Management
Computacenter
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: *.*.