Comparison Overview
FILA

FILA
US
Last Update: 28/03/2026
In 2021, FILA commemorates its 110th Anniversary. Over the last half century, FILA has been there for iconic moments, accompanying extraordinary individuals in pursuit of sport – those who courageously challenge limits and defy expectations through a seamless combinat...

J.Crew
225 Liberty St, New York, New York, US, 10281
Last Update: 29/03/2026
Since 1983, we’ve been designing pieces that feel both familiar and refreshingly new, crafted with unbeatable quality and distinctive point of view...it’s no wonder we’ve been in your closet for four decades and counting. Today, we continue to do the classics our way, ...
Compliance Ranges Comparison

FILA







J.Crew






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

FILA

J.Crew
FAQ
Latest Global CVEs
Use after free in Aura in Google Chrome prior to 150.0.7871.128 allowed a local attacker to potentially exploit heap corruption via a malicious file. (Chromium security severity: High)
Use after free in Ozone in Google Chrome on Linux prior to 150.0.7871.128 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
Out of bounds read and write in V8 in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Use after free in Cast in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Use after free in Network in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)