Comparison Overview
Frasers Group
Frasers Group
Academy House, 36 Poland Street, London , W1F 7LU, GB
Last Update: 08/09/2026
Frasers Group started as a small store in Maidenhead in 1982 and from there, grew to become a global powerhouse. We are now a collection of the world’s most iconic brands including Sports Direct, Flannels, GAME, Jack Wills, Sofa.com, Evans Cycles, USC, and Everlast. W...
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
Frasers Group
Canadian Tire Corporation
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Frasers Group in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Canadian Tire Corporation in 2026.
Incident History - Frasers Group (X = Date, Y = Severity)
Frasers Group 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
Frasers Group
Canadian Tire Corporation
FAQ
Latest Global CVEs
vLLM through 0.29.0 fails to properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/push_worker.py#L162-L181
- https://github.com/vllm-project/vllm/pull/55677
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-rejected-requests
redis-parser through 3.0.0 contains a denial of service vulnerability in the RESP protocol parser that allows malicious Redis endpoints to crash the client process through unbounded recursion on nested arrays. Attackers can send crafted RESP byte streams with repeated array headers that exhaust the V8 call stack, causing an uncaught RangeError that terminates the Node.js process without triggering error handling callbacks.
- https://github.com/NodeRedis/node-redis-parser
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L204-L213
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L291-L306
- https://github.com/redis/ioredis/issues/2108
- https://www.vulncheck.com/advisories/redis-parser-through-3.0.0-denial-of-service-via-unbounded-recursion
Improper neutralization of special elements in output used by a downstream component ('injection') in Azure Cosmos DB allows an authorized attacker to elevate privileges over a network.
Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.