Comparison Overview
Orkla Snacks Norge AS

Orkla Snacks Norge AS
Drammensveien 149, Oslo, undefined, 0277, NO
Last Update: 25/02/2026
Orkla Snacks Norway consists of the former companies Nidar, Sætre and KiMs Norway. The company has strong positions in snacks, sweets and biscuits in Norway. We develop, manufacture and market well-known and beloved brands for enjoyment and pleasure as f.ex. Nidar fa...

Godrej Enterprises Group
N/A
Last Update: 01/04/2026
Since 1897, Godrej Enterprises Group (which includes Godrej & Boyce and its affiliates) has contributed significantly to India’s economic growth and self-reliance by providing complex engineering, design led innovation, and sustainable manufacturing solutions. From the ...
Compliance Ranges Comparison

Orkla Snacks Norge AS







Godrej Enterprises Group






Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Orkla Snacks Norge AS in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Godrej Enterprises Group in 2026.
Incident History - Orkla Snacks Norge AS (X = Date, Y = Severity)
Orkla Snacks Norge AS cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Godrej Enterprises Group (X = Date, Y = Severity)
Godrej Enterprises Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Orkla Snacks Norge AS

Godrej Enterprises Group
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: *.*.