Comparison Overview
Watsons Turkey
Watsons Turkey
Saray Mah. Site Yolu Cad. Anel İş Merkezi No:5 Kat:4-5, İstanbul, undefined, 34768, TR
Last Update: 19/03/2026
Watsons Türkiye is part of AS Watson Group, the world’s largest international health and beauty retailer operating over 16,800 stores under 12 retail brands in 30 markets, with over 130,000 employees worldwide. For the fiscal year 2023, AS Watson Group recorded revenue ...
Sainsbury's
33 Holborn, London, EC1N 2HT, GB
Last Update: 01/04/2026
Over 150 years old and still going strong, we’re the UK’s second-biggest retailer. Every day, the nation shops with us because they know they’ll get affordable, good food and excellent service. We focus on great value and convenient shopping across our family of brands...
Compliance Ranges Comparison
Watsons Turkey
Sainsbury's
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Watsons Turkey in 2026.
Incidents vs Retail Industry Avg (This Year)
Sainsbury's has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Watsons Turkey (X = Date, Y = Severity)
Watsons Turkey cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sainsbury's (X = Date, Y = Severity)
Sainsbury's cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Watsons Turkey
Sainsbury's
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: *.*.