Comparison Overview
Publix Super Markets
Publix Super Markets
3300 Publix Corporate Parkway, Lakeland, 33811, US
Last Update: 01/04/2026
Founded in 1930, Publix Super Markets is the largest and fastest-growing employee-owned supermarket chain in the United States. Publix employs over 200,000 associates. We are privately-owned, hold no long-term debt, have avoided layoffs, and continue to grow year after ...
SPAR International
Rokin 99, Amsterdam, 1012KM, NL
Last Update: 01/04/2026
The worldwide SPAR organisation operates over 13,800 SPAR stores in 48 countries on four continents, meeting the needs of over 14,7 million consumers every day. The SPAR concept was established on the basis of wholesalers and retailers working in partnership to the be...
Compliance Ranges Comparison
Publix Super Markets
SPAR International
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Publix Super Markets in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for SPAR International in 2026.
Incident History - Publix Super Markets (X = Date, Y = Severity)
Publix Super Markets cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SPAR International (X = Date, Y = Severity)
SPAR International cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Publix Super Markets
SPAR International
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: *.*.