Comparison Overview
SUSE
SUSE
Frankenstraße 146, Nürnberg, 90461, DE
Last Update: 08/05/2026
SUSE is a global leader in innovative, reliable and secure enterprise open source solutions, including SUSEⓇ Linux Suite, SUSEⓇ Rancher Suite, SUSEⓇ Edge Suite and SUSEⓇ AI Suite. More than 60% of the Fortune 500 rely on SUSE to power their mission-critical workloads, e...
Wolt
Pohjoinen Rautatiekatu 21, Helsinki, Uusimaa, FI, 00100
Last Update: 01/04/2026
Wolt is a Helsinki-based technology company with a mission to bring joy, simplicity and earnings to the neighborhoods of the world. Wolt develops a local commerce platform that connects people looking to order food, groceries, and other goods with people interested in s...
Compliance Ranges Comparison
SUSE
Wolt
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
SUSE has 86.92% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Wolt in 2026.
Incident History - SUSE (X = Date, Y = Severity)
SUSE cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Wolt (X = Date, Y = Severity)
Wolt cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
SUSE
Wolt
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: *.*.