Comparison Overview
Sally Beauty
Sally Beauty
3001 Colorado Blvd., Denton, 76210, US
Last Update: 01/04/2026
Sally Beauty Holdings, Inc. (“Sally”) through its affiliates is the world’s largest distributor of professional beauty supplies. Sally provides the channels that allow manufacturers of beauty supplies to reach customers, both professional and non-professional. Sall...
REWE Group
Domstraße 20, Köln, 50668, DE
Last Update: 02/04/2026
The cooperatively organized REWE Group is one of the leading trade and tourism groups in Germany and Europe. In 2024, the company generated a total external turnover of more than 96 billion euros. Founded in 1927, REWE Group operates with around 380,000 employees in 21 ...
Compliance Ranges Comparison
Sally Beauty
REWE Group
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Sally Beauty in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for REWE Group in 2026.
Incident History - Sally Beauty (X = Date, Y = Severity)
Sally Beauty cyber incidents detection timeline including parent company and subsidiaries.
Incident History - REWE Group (X = Date, Y = Severity)
REWE Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Sally Beauty
REWE Group
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: *.*.