Comparison Overview
REFASH
REFASH
79 Ayer Rajah Crescent, Singapore, 139955, SG
Last Update: 17/04/2026
At REFASH, we believe fashion can be a force for good. Thrifting isn’t just about scoring great deals—it’s about shopping with purpose and embracing sustainability. Since our founding in 2016, our mission has been clear: to inspire a new generation of consumers to thin...
Lidl France
1, Rue de Hanovre, Châtenay-Malabry, 92290, FR
Last Update: 04/04/2026
Lidl s’est implanté en France en 1989. Nous avons connu une expansion très rapide qui nous a permis de devenir un acteur incontournable de la grande distribution. Lidl France, c’est aujourd’hui 45 000 collaborateurs, plus de 1 570 magasins, 25 Directions Régionales et ...
Compliance Ranges Comparison
REFASH
Lidl France
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for REFASH in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Lidl France in 2026.
Incident History - REFASH (X = Date, Y = Severity)
REFASH cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lidl France (X = Date, Y = Severity)
Lidl France cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
REFASH
Lidl France
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: *.*.