Comparison Overview
Medirest Signature
Medirest Signature
Rivermead, Uxbridge, UB9 4BF, GB
Last Update: 25/12/2025
Specialists in creating a high-quality patient experience, Medirest Signature brings together fine dining, housekeeping, security and concierge services — all tailored for private healthcare.
Sodexo
255 quai de la bataille de Stalingrad, 92866 Issy les Moulineaux Cedex 9, FR
Last Update: 02/04/2026
Founded in Marseille in 1966 by Pierre Bellon, Sodexo is the leader in Food and Services, shaping better everyday experiences at every moment in life: work, heal, learn and play. The Group stands out for its independence, its founding family shareholding and its respons...
Compliance Ranges Comparison
Medirest Signature
Sodexo
Benchmark & Cyber Underwriting Signals
Incidents vs Facilities Services Industry Avg (This Year)
No incidents recorded for Medirest Signature in 2026.
Incidents vs Facilities Services Industry Avg (This Year)
No incidents recorded for Sodexo in 2026.
Incident History - Medirest Signature (X = Date, Y = Severity)
Medirest Signature cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sodexo (X = Date, Y = Severity)
Sodexo cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Medirest Signature
Sodexo
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: *.*.