Comparison Overview
Foot Locker EMEA

Foot Locker EMEA
Stationsplein 32, Utrecht, Utrecht, 3511 ED, NL
Last Update: 10/12/2025
Foot Locker, Inc. is a leading footwear and apparel retailer that unlocks the “inner sneakerhead” in all of us. With approximately 2500 retail stores in 26 countries across North America, Europe, Asia, Australia, and New Zealand, and a franchised store presence in the M...

Coop
Thiersteinerallee 14, Basel, 4002, CH
Last Update: 07/09/2026
Coop has been an integral part of Switzerland for over 150 years and acts with a sense of responsibility for its people, its regions and its ecosystems. As a retailer, wholesaler and producer, we deliver quality and are proud of our numerous brands and products. The div...
Compliance Ranges Comparison

Foot Locker EMEA







Coop






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Foot Locker EMEA in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Coop in 2026.
Incident History - Foot Locker EMEA (X = Date, Y = Severity)
Foot Locker EMEA cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Coop (X = Date, Y = Severity)
Coop cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Foot Locker EMEA

Coop
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.