Comparison Overview
Orkla Health
Orkla Health
Drammensveien 149, Oslo, 0277, NO
Last Update: 09/01/2026
Orkla Health is one of Europe’s leading branded consumer health companies. With a diverse portfolio of products ranging from supplements to wound care, oral care and healthcare solutions, our 1,850 employees serve our customers through a multi-channel set-up in more tha...
DICK'S Sporting Goods
345 Court Street, Coraopolis, PA, US, 15108
Last Update: 02/04/2026
YOU LIVE AND BREATHE SPORTS. SO DO WE. In work and in life. On the field, the court or the ice. Nothing wins like a commitment to excellence; to your team and your goals. At DICK’S Sporting Goods, it’s this kind of thinking that inspires our mission. Our culture is t...
Compliance Ranges Comparison
Orkla Health
DICK'S Sporting Goods
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Orkla Health in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for DICK'S Sporting Goods in 2026.
Incident History - Orkla Health (X = Date, Y = Severity)
Orkla Health cyber incidents detection timeline including parent company and subsidiaries.
Incident History - DICK'S Sporting Goods (X = Date, Y = Severity)
DICK'S Sporting Goods cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Orkla Health
DICK'S Sporting Goods
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: *.*.