Comparison Overview
Selfridges
Selfridges
400 Oxford Street, London, England, GB, W1A 1AB
Last Update: 12/03/2026
Founded in 1909 by American entrepreneur Harry Gordon Selfridge, Selfridges is widely recognised as the original and finest example of the modern department store. For over a century, Selfridges has stood as a retail icon and a landmark of British culture, redefining ...
Tesco
Shire Park, Welwyn Garden City, AL7 1GA, GB
Last Update: 09/07/2026
One of the world’s largest retailers of consumer goods from food to fashion. Serving our customers, communities and planet a little better every day in our stores and online is at the heart of everything we do. Founded in 1919 by Jack Cohen using the £30 he received on...
Compliance Ranges Comparison
Selfridges
Tesco
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Selfridges in 2026.
Incidents vs Retail Industry Avg (This Year)
Tesco has 4.76% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Selfridges (X = Date, Y = Severity)
Selfridges cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Tesco (X = Date, Y = Severity)
Tesco cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Selfridges
Tesco
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.