Comparison Overview
Under Armour

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...

C&A
Wanheimer Strasse 70, Düsseldorf, NRW, DE, 40468
Last Update: 31/03/2026
Ever since our founding by the brothers Clemens and August in 1841, C&A has been at the forefront of fashion. From making 'ready-to-wear' a thing when custom-made was the norm, to popularising miniskirts in the 60s, introducing the Com-bi-kini in the 70s, Bio Cotton in...
Compliance Ranges Comparison

Under Armour







C&A






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
Under Armour has 58.51% 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 C&A in 2026.
Incident History - Under Armour (X = Date, Y = Severity)
Under Armour cyber incidents detection timeline including parent company and subsidiaries.
Incident History - C&A (X = Date, Y = Severity)
C&A cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Under Armour

C&A
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)