Comparison Overview
Capgemini Customer Experience
Capgemini Customer Experience
11 rue de Tilsitt, Paris, 75017, FR
Last Update: 10/03/2026
The Capgemini Customer Experience (CX) proposition and suite of offerings allow our clients to transform their relationships with their customers and create experiences which provide rapid and sustainable value, both for their end-customer and their own organization. O...
Lenovo
8001 Development Dr, Morrisville, 27560, US
Last Update: 01/04/2026
Lenovo is a US$69 billion revenue global technology powerhouse, ranked #196 in the Fortune Global 500, and serving millions of customers every day in 180 markets. Focused on a bold vision to deliver Smarter Technology for All, Lenovo has built on its success as the worl...
Compliance Ranges Comparison
Capgemini Customer Experience
Lenovo
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Capgemini Customer Experience in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Lenovo has 4.76% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Capgemini Customer Experience (X = Date, Y = Severity)
Capgemini Customer Experience cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lenovo (X = Date, Y = Severity)
Lenovo cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Capgemini Customer Experience
Lenovo
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: *.*.