Comparison Overview
Dollarama
Dollarama
5805 Royalmount, Mont-Royal, H4P 0A1, CA
Last Update: 07/10/2026
Dollarama was founded by third-generation retailer and Canadian entrepreneur, Larry Rossy. It all started with one store, in Matane, Quebec, in 1992, and quickly grew over the next two decades to become a household name and shopping destination for Canadians from coast ...
Jewel-Osco
150 Pierce Road, Itasca, 60143, US
Last Update: 02/04/2026
Proudly serving our customers in the Chicagoland area since 1899, Jewel-Osco provides friendly service, quality products and great value. Jewel-Osco operates 188 stores throughout the Chicagoland area, Indiana and Iowa, which is part of a 2,200+ store operation that emp...
Compliance Ranges Comparison
Dollarama
Jewel-Osco
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Dollarama in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Jewel-Osco in 2026.
Incident History - Dollarama (X = Date, Y = Severity)
Dollarama cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Jewel-Osco (X = Date, Y = Severity)
Jewel-Osco cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Dollarama
Jewel-Osco
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.