Comparison Overview
DRIES VAN NOTEN
DRIES VAN NOTEN
Godefriduskaai, Antwerp, Belgium, 2000, BE
Last Update: 08/02/2026
Dries Van Noten is a well-known brand in the fashion industry. He established in 1986 his own label and opened his first boutique in the Belgian fashion capital, Antwerp. In 1993 he brought his women’s collection to the Paris runways for the first time. Today, he has ow...
Bata Group
Avenue d'ouchy 61, Lausanne, 1006, CH
Last Update: 01/04/2026
The Bata Group is one of the world's leading manufacturers and retailers of quality footwear. A global concern with more than 32,000 employees, 21 production facilities, over 5,300 stores in more than 70 countries across the globe, Bata has been providing the best shoes...
Compliance Ranges Comparison
DRIES VAN NOTEN
Bata Group
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
No incidents recorded for DRIES VAN NOTEN in 2026.
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
No incidents recorded for Bata Group in 2026.
Incident History - DRIES VAN NOTEN (X = Date, Y = Severity)
DRIES VAN NOTEN cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bata Group (X = Date, Y = Severity)
Bata Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
DRIES VAN NOTEN
Bata 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: *.*.