Comparison Overview
Mansion House Consulting
Mansion House Consulting
14-16 Dowgate Hill, London, undefined, EC4R 2SU, GB
Last Update: 20/12/2025
Mansion House Consulting (MHC) is an international business and technology Consultancy focused exclusively on the Financial Services sector. We provide high quality, practical and robust solutions to all areas of the industry through our teams of highly qualified consul...
Capgemini Invent
Place de l'Etoile, 11 rue de Tilsitt, Paris, FR, 75017
Last Update: 02/04/2026
Capgemini Invent is the digital innovation, consulting and transformation brand of the Capgemini Group, a global business line that combines market leading expertise in strategy, technology, data science and creative design, to help CxOs envision and build what’s next f...
Compliance Ranges Comparison
Mansion House Consulting
Capgemini Invent
Benchmark & Cyber Underwriting Signals
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for Mansion House Consulting in 2026.
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for Capgemini Invent in 2026.
Incident History - Mansion House Consulting (X = Date, Y = Severity)
Mansion House Consulting cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Capgemini Invent (X = Date, Y = Severity)
Capgemini Invent cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Mansion House Consulting
Capgemini Invent
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: *.*.