Comparison Overview
Urban Outfitters
Urban Outfitters
5000 S. Broad St, Philadelpia, PA, US, 19112
Last Update: 03/04/2026
Urban Outfitters is a global lifestyle brand dedicated to fueling the next generation’s individuality through a unique blend of product, creativity, music, and youth culture. Founded in 1970 in a small space across from the University of Pennsylvania, Urban Outfitters n...
HUGO BOSS
Holy-Allee 3, Metzingen, Baden-Württemberg, DE, 72555
Last Update: 02/04/2026
At HUGO BOSS, we firmly believe that the passion and dedication of our employees is the essence for the successful execution of our “CLAIM 5 TOUCHDOWN” growth strategy. A strong commitment to empowering people and teams is therefore firmly anchored in “CLAIM 5 TOUCHDOWN...
Compliance Ranges Comparison
Urban Outfitters
HUGO BOSS
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
Urban Outfitters has 66.67% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
No incidents recorded for HUGO BOSS in 2026.
Incident History - Urban Outfitters (X = Date, Y = Severity)
Urban Outfitters cyber incidents detection timeline including parent company and subsidiaries.
Incident History - HUGO BOSS (X = Date, Y = Severity)
HUGO BOSS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Urban Outfitters
HUGO BOSS
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: *.*.