Comparison Overview
METRO France
METRO France
5 rue des Grands Prés, Nanterre, 92000, FR
Last Update: 26/12/2025
Do you know METRO? We are number 1 in France and independant restaurant owners' first omnichannel choice of independent restaurant owners, retailers. We are 9,000 employees to service taste entrepreneurs ! We care about the quality of our products, a relationship base...
Rexel
13, Boulevard du Fort de Vaux, Paris, Île-de-France, FR, 75017
Last Update: 02/04/2026
Rexel, worldwide expert in the multichannel professional distribution of products and services for the energy world, addresses three main markets: residential, commercial, and industrial. The Group supports its residential, commercial, and industrial customers by provid...
Compliance Ranges Comparison
METRO France
Rexel
Benchmark & Cyber Underwriting Signals
Incidents vs Wholesale Industry Avg (This Year)
No incidents recorded for METRO France in 2026.
Incidents vs Wholesale Industry Avg (This Year)
No incidents recorded for Rexel in 2026.
Incident History - METRO France (X = Date, Y = Severity)
METRO France cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Rexel (X = Date, Y = Severity)
Rexel cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
METRO France
Rexel
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: *.*.