Comparison Overview
Pottery Barn

Pottery Barn
151 Union Street, San Francisco, CA, 94111, US
Last Update: 15/11/2025
For over 70 years, Pottery Barn has represented exceptional quality and unparalleled value. America’s most meaningful, beautiful design source, we bring together good products, people and values. We believe that style evolves, but quality is timeless. Original designs...

Canadian Tire Corporation
2180 Yonge St, Toronto, Ontario, CA, M4S 2B9
Last Update: 10/09/2026
Canadian Tire Corporation, Limited (“CTC”) is one of Canada’s most admired and trusted companies. With world-class owned brands and exciting market-leading merchandising strategies, we are continually innovating with purpose: to be there for Canadians from coast-to-coas...
Compliance Ranges Comparison

Pottery Barn







Canadian Tire Corporation






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

Pottery Barn

Canadian Tire Corporation
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.