Comparison Overview
Brown Thomas Arnotts
Brown Thomas Arnotts
None, None, Dublin, Ireland, IE, '
Last Update: 27/02/2026
Brown Thomas Arnotts is Ireland's leading luxury fashion retailer. We're a retail world built on iconic firsts, famed for the creativity that touches our brands, buildings and experiences. We’re always challenging ourselves to make every experience more special and uniq...
SPAR South Africa
22 Chancery Lane, Pinetown, KwaZulu-Natal, ZA, 3610
Last Update: 01/04/2026
There’s something different about shopping at SPAR, that’s because we’ve created a culture of caring and community to ensure our customers have a consistently enjoyable shopping experience in a uniquely friendly and family orientated store. Nothing means more to us th...
Compliance Ranges Comparison
Brown Thomas Arnotts
SPAR South Africa
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Brown Thomas Arnotts in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for SPAR South Africa in 2026.
Incident History - Brown Thomas Arnotts (X = Date, Y = Severity)
Brown Thomas Arnotts cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SPAR South Africa (X = Date, Y = Severity)
SPAR South Africa cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Brown Thomas Arnotts
SPAR South Africa
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: *.*.