Comparison Overview
Woolworths New Zealand
Woolworths New Zealand
N/A
Last Update: 17/02/2026
We are Aotearoa’s leading supermarket brand, across 185 stores we serve about 3 million customers every week. It’s a big job, but we love what we do - giving customers the very best in choice, value and convenience, while keeping our social and environmental responsibil...
Jumbo
Av Kennedy, Santiago, 83335, CL
Last Update: 02/04/2026
Con un tamaño promedio de 8.250 m2, Hipermercados Jumbo ofrece un variado surtido de productos, que incluye alimentos, abarrotes y una amplia gama de artículos no comestibles, como vestuario, elementos para el hogar y electrodomésticos. Además de las marcas tradicionale...
Compliance Ranges Comparison
Woolworths New Zealand
Jumbo
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Groceries Industry Avg (This Year)
No incidents recorded for Woolworths New Zealand in 2026.
Incidents vs Retail Groceries Industry Avg (This Year)
No incidents recorded for Jumbo in 2026.
Incident History - Woolworths New Zealand (X = Date, Y = Severity)
Woolworths New Zealand cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Jumbo (X = Date, Y = Severity)
Jumbo cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Woolworths New Zealand
Jumbo
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: *.*.