Comparison Overview
Sodimac

Sodimac
Chile, Brasil, Perú, Argentina, Uruguay, Colombia, México, CL
Last Update: 01/04/2026
#SomosUnEquipo Te invitamos a conocer y a ser parte de nuestra Casa, un lugar donde la innovación, la sostenibilidad y la diversidad se viven día a día. Con más de 60 años de trayectoria y presencia en Chile, Perú, Colombia, Argentina, Brasil, Uruguay y México, nuestra ...

Kmart Australia Limited
690 Springvale Road, MULGRAVE, VIC, AU, 3170
Last Update: 02/04/2026
We’re Team Kmart, on a mission to make everyday living brighter for our customers by improving the Kmart shopping experience – every time and everywhere they engage with us. For over fifty years now, we’ve been spreading the Kmart love to families of all shapes and si...
Compliance Ranges Comparison

Sodimac







Kmart Australia Limited






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Sodimac in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Kmart Australia Limited in 2026.
Incident History - Sodimac (X = Date, Y = Severity)
Sodimac cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Kmart Australia Limited (X = Date, Y = Severity)
Kmart Australia Limited cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Sodimac

Kmart Australia Limited
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: *.*.