Comparison Overview
Osuuskauppa Suur-Savo

Osuuskauppa Suur-Savo
Maaherrankatu 13, Mikkeli, 50100, FI
Last Update: 03/12/2025
Osuuskauppa Suur-Savo on yli 70 000:n asiakasomistajan omistama yritys, joka toimii Etelä-Savossa 11 kunnan alueella. Toimialueemme kattaa Mikkelin, Pieksämäen ja Savonlinnan talousalueet. Jo yli 79 % toimialueen talouksista on osuuskauppamme asiakasomistajia. Toimialo...

H&M
Vasagatan 7, Stockholm, Stockholm County, SE, 111 20
Last Update: 05/06/2026
At H&M, we welcome you to be yourself and feel like you truly belong. Help us reimagine the future of an entire industry by making everyone look, feel, and do good. We take pride in our history of making fashion accessible to everyone and led by our values we strive to...
Compliance Ranges Comparison

Osuuskauppa Suur-Savo







H&M






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

Osuuskauppa Suur-Savo

H&M
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: *.*.