Comparison Overview
Miles & More GmbH

Miles & More GmbH
MAC - Main Airport Center, Frankfurt am Main, undefined, 60549, DE
Last Update: 18/02/2026
30 years of experience in the loyalty sector and more than 25 years in the retail business make Miles & More GmbH an expert in personalised customer targeting and retention. Our vision is to shape loyalty for future generations. We are a wholly-owned subsidiary of Deuts...

Great Clips Inc.
4400 W. 78th St., Minneapolis, 55435, US
Last Update: 02/04/2026
Established in Minneapolis in 1982, Great Clips has grown to be the world's largest and fastest growing salon brand. There are more than 4,400 salons throughout the United States and Canada -- all of them owned by franchisees. Visit us at www.greatclips.com Employment ...
Compliance Ranges Comparison

Miles & More GmbH







Great Clips Inc.






Benchmark & Cyber Underwriting Signals
Incidents vs Consumer Services Industry Avg (This Year)
No incidents recorded for Miles & More GmbH in 2026.
Incidents vs Consumer Services Industry Avg (This Year)
No incidents recorded for Great Clips Inc. in 2026.
Incident History - Miles & More GmbH (X = Date, Y = Severity)
Miles & More GmbH cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Great Clips Inc. (X = Date, Y = Severity)
Great Clips Inc. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Miles & More GmbH

Great Clips Inc.
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: *.*.