Comparison Overview
Springfield

Springfield
Avda. Llano Castellano, 51, Madrid, Madrid, 28034, ES
Last Update: 23/02/2026
De espíritu europeo, Springfield nace en 1988 como marca de casualwear ofreciendo un estilo urbano de atractivo contemporáneo y dirigida a hombres y mujeres en todo el mundo entre los 25- 35 años. Una marca para gente real y con actitud en su día a día, que está fuerte...

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

Springfield







Under Armour






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
No incidents recorded for Springfield in 2026.
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
Under Armour has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Springfield (X = Date, Y = Severity)
Springfield 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

Springfield

Under Armour
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)