Comparison Overview
HUGO BOSS

HUGO BOSS
Holy-Allee 3, Metzingen, Baden-Württemberg, DE, 72555
Last Update: 10/09/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...

Under Armour
101 Performance Dr, Baltimore, 21230, US
Last Update: 11/09/2026
Our Belief: WE USE THE POWER OF SPORTS TO EXPAND EVERY PLAYING FIELD. Our Obsession: WE ARE OBSESSED WITH ATHLETES WHO STRIVE FOR MORE – IN SPORTS, IN LIFE, AND IN THE WORLD. Our Mission: TO INSPIRE ATHLETES WITH INNOVATIVE PERFORMANCE AND DESIGN SOLUTIONS THEY CAN’T LI...
Compliance Ranges Comparison

HUGO BOSS







Under Armour






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
No incidents recorded for HUGO BOSS in 2026.
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
Under Armour has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - HUGO BOSS (X = Date, Y = Severity)
HUGO BOSS cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Under Armour (X = Date, Y = Severity)
Under Armour cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

HUGO BOSS

Under Armour
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout