Comparison Overview
ONLY BRAND HOUSE

ONLY BRAND HOUSE
Fredskovvej 1, Brande, Danmark 7330, DK
Last Update: 21/04/2026
ONLY was established in 1995 as a part of the BESTSELLER group. From the beginning, the vision of ONLY was to dominate the fashion industry with amazing fits, affordable styles, and simply great denim. More than 25 years later, ONLY has turned into a complete Brand Hous...

BESTSELLER
Fredskovvej, Brande, undefined, DK-7330, DK
Last Update: 31/03/2026
At BESTSELLER, we are more than 22,000 people in 38 different countries working for over 20 fashion brands such as ONLY, JACK & JONES, VERO MODA, NAME IT, SELECTED, VILA, PIECES, OBJECT, MAMALICIOUS, NOISY MAY and Y.A.S. We are a family-owned company with a strong found...
Compliance Ranges Comparison

ONLY BRAND HOUSE







BESTSELLER






Benchmark & Cyber Underwriting Signals
Incidents vs Apparel & Fashion Industry Avg (This Year)
No incidents recorded for ONLY BRAND HOUSE in 2026.
Incidents vs Apparel & Fashion Industry Avg (This Year)
No incidents recorded for BESTSELLER in 2026.
Incident History - ONLY BRAND HOUSE (X = Date, Y = Severity)
ONLY BRAND HOUSE cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BESTSELLER (X = Date, Y = Severity)
BESTSELLER cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

ONLY BRAND HOUSE

BESTSELLER
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: *.*.