Comparison Overview
SAS Retail Services
SAS Retail Services
1575 North Main St, Orange, California, 92867, US
Last Update: 07/04/2026
We’re here to make your impossible, #possible at retail. Any Store. Any Aisle. Any Service. Today, every day, team SAS Retail Services actualizes vision —for retailer and CPG partners across the U.S., Canada, and in Asia. As change agents in an industry of change, we ...
Specsavers
La Villiaize, St Andrews, Global, GB, GY6 8YP
Last Update: 02/04/2026
Specsavers began 40 years ago with the vision of two optometrists, Doug and Mary Perkins, who set out to provide best-value eyecare to everybody. Their passion for optometry has led Specsavers to become the largest privately-owned optical group in the world, deliverin...
Compliance Ranges Comparison
SAS Retail Services
Specsavers
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for SAS Retail Services in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Specsavers in 2026.
Incident History - SAS Retail Services (X = Date, Y = Severity)
SAS Retail Services cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Specsavers (X = Date, Y = Severity)
Specsavers cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
SAS Retail Services
Specsavers
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: *.*.