Comparison Overview
Coop
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...
Vans
1588 South Coast Dr, Costa Mesa, 92626, US
Last Update: 14/09/2026
Vans is a globally iconic skate brand, forever rooted in the authentic lifestyle of skateboarding. We are driven by our mission to inspire and empower everyone to live “Off The Wall” – embracing the youthful spirit of freedom, non-conformity, and relentless progression....
Compliance Ranges Comparison
Coop
Vans
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Coop in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Vans in 2026.
Incident History - Coop (X = Date, Y = Severity)
Coop cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Vans (X = Date, Y = Severity)
Vans cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Coop
Vans
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.